Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92f90d62d0d0b9cf61de313157084938b6ef485c0278a2d2380b7030eae35e2b

Tx prefix hash: 494d742ae9815f5946016b0bbc10d83e5e5f3b2f20ab0991f1f2ccee95a4e20c
Tx public key: b966efd1df5154da4f88ee4d76858aa071289d709cf70afbe738adb6503eee17
Timestamp: 1707454133 Timestamp [UCT]: 2024-02-09 04:48:53 Age [y:d:h:m:s]: 01:271:19:14:47
Block: 953536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453019 RingCT/type: yes/0
Extra: 01b966efd1df5154da4f88ee4d76858aa071289d709cf70afbe738adb6503eee1702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: e537bf2ebf79e6f41f1b65a225ed7608a54cb6e9b8031699d00c04d7debfcb1c 0.600010000000 1412758 of 0

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": 953546, "vin": [ { "gen": { "height": 953536 } } ], "vout": [ { "amount": 600010000, "target": { "key": "e537bf2ebf79e6f41f1b65a225ed7608a54cb6e9b8031699d00c04d7debfcb1c" } } ], "extra": [ 1, 185, 102, 239, 209, 223, 81, 84, 218, 79, 136, 238, 77, 118, 133, 138, 160, 113, 40, 157, 112, 156, 247, 10, 251, 231, 56, 173, 182, 80, 62, 238, 23, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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