Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6cde39787fc394ca384492518240fa7360cac83377efb2b3e753d7620f9636a1

Tx prefix hash: 4bd04589ca4bf5d1e96793bdd927c21586ad5fdfc4acde5b4bfcfc121b4d8cbe
Tx public key: 295d83c22fc8d4a9e6600e8b34afcd38f3524770c10aeea18683a9e92b79b8f5
Timestamp: 1731891415 Timestamp [UCT]: 2024-11-18 00:56:55 Age [y:d:h:m:s]: 00:215:11:11:20
Block: 1156053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153685 RingCT/type: yes/0
Extra: 01295d83c22fc8d4a9e6600e8b34afcd38f3524770c10aeea18683a9e92b79b8f50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03f1013a6b1ae97e2f7591fa861954a59f815b1465cd172abc36dc4aeb2b9a64 0.600000000000 1641672 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1156063, "vin": [ { "gen": { "height": 1156053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03f1013a6b1ae97e2f7591fa861954a59f815b1465cd172abc36dc4aeb2b9a64" } } ], "extra": [ 1, 41, 93, 131, 194, 47, 200, 212, 169, 230, 96, 14, 139, 52, 175, 205, 56, 243, 82, 71, 112, 193, 10, 238, 161, 134, 131, 169, 233, 43, 121, 184, 245, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8