Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 907eff1bbc77358a69d061f354bf9321f3d1fcd7025880637e7837e3e38d448d

Tx prefix hash: 730c671b9ad96a980030c915b862b15a5b930d7ee31e69ccff42f9c9e3779c6b
Tx public key: 0bea0e61f8a2ef7a88de6ee62baa998003e1fb4697edcf02455b56684092434f
Timestamp: 1764623398 Timestamp [UCT]: 2025-12-01 21:09:58 Age [y:d:h:m:s]: 00:002:05:38:03
Block: 1424374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1598 RingCT/type: yes/0
Extra: 010bea0e61f8a2ef7a88de6ee62baa998003e1fb4697edcf02455b56684092434f021100000005defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 417472aca43ab6b9d3d11c31dd6d2eb8e70d8bb9fc486cc7ab71afb9f3d1eef1 0.600000000000 1913005 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": 1424384, "vin": [ { "gen": { "height": 1424374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "417472aca43ab6b9d3d11c31dd6d2eb8e70d8bb9fc486cc7ab71afb9f3d1eef1" } } ], "extra": [ 1, 11, 234, 14, 97, 248, 162, 239, 122, 136, 222, 110, 230, 43, 170, 153, 128, 3, 225, 251, 70, 151, 237, 207, 2, 69, 91, 86, 104, 64, 146, 67, 79, 2, 17, 0, 0, 0, 5, 222, 251, 143, 24, 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