Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9afa92395e82cebb6abb28ff68bee25c6bb515011193b92bb6a1081f9d3f10cc

Tx prefix hash: 62ad5ef4ba62b55e6bb0178174f928f2258d40b2d97b3e19b194de89fe8e1a83
Tx public key: 0b790c4ef58eabf98d2d8a06f02ce2a41167be6966583a38fa54cd3d93ea5f4b
Timestamp: 1743839053 Timestamp [UCT]: 2025-04-05 07:44:13 Age [y:d:h:m:s]: 00:230:09:34:34
Block: 1254699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162391 RingCT/type: yes/0
Extra: 010b790c4ef58eabf98d2d8a06f02ce2a41167be6966583a38fa54cd3d93ea5f4b0211000000094060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64e5a3d70b1ed30971ffd786355f2c8c73e831ab3c9dad74846d5208e211be95 0.600000000000 1741780 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": 1254709, "vin": [ { "gen": { "height": 1254699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64e5a3d70b1ed30971ffd786355f2c8c73e831ab3c9dad74846d5208e211be95" } } ], "extra": [ 1, 11, 121, 12, 78, 245, 142, 171, 249, 141, 45, 138, 6, 240, 44, 226, 164, 17, 103, 190, 105, 102, 88, 58, 56, 250, 84, 205, 61, 147, 234, 95, 75, 2, 17, 0, 0, 0, 9, 64, 96, 246, 210, 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