Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59e8dfcb790a311b5c4e244f59724d4c68a931aa05fcd4a53df609d350d90979

Tx prefix hash: edd73e4c3ba876074ba2ffdd19b271c942fceafde13c654ee6d1ea219e4c7221
Tx public key: 5707ec44cb5bd74790554be942d196dc8953cd69e72114e434a3d250d8a14e84
Timestamp: 1737403265 Timestamp [UCT]: 2025-01-20 20:01:05 Age [y:d:h:m:s]: 00:148:02:57:49
Block: 1201651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105595 RingCT/type: yes/0
Extra: 015707ec44cb5bd74790554be942d196dc8953cd69e72114e434a3d250d8a14e840211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd10e87efbe1229fbe86926da9fc1091b5a2a5a96a2cff200d3f7a61e6072190 0.600000000000 1688308 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": 1201661, "vin": [ { "gen": { "height": 1201651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd10e87efbe1229fbe86926da9fc1091b5a2a5a96a2cff200d3f7a61e6072190" } } ], "extra": [ 1, 87, 7, 236, 68, 203, 91, 215, 71, 144, 85, 75, 233, 66, 209, 150, 220, 137, 83, 205, 105, 231, 33, 20, 228, 52, 163, 210, 80, 216, 161, 78, 132, 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