Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d968ba3b7124da84c8d9df8605f01eb022cf5d35474f29f6ffa5e198c30140b

Tx prefix hash: 827d5f98e11ba68df3a5a23ea3a145a5ed9a8d41a2d4f29f772863402e249388
Tx public key: 817e02e81acb160b2d8d8834220c428db18e3619d8a60db0aa89f987d846ef8c
Timestamp: 1662065614 Timestamp [UCT]: 2022-09-01 20:53:34 Age [y:d:h:m:s]: 02:130:15:42:14
Block: 578754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614849 RingCT/type: yes/0
Extra: 01817e02e81acb160b2d8d8834220c428db18e3619d8a60db0aa89f987d846ef8c02110000000175e3f0e9000000000000000000

1 output(s) for total of 7.419042107000 dcy

stealth address amount amount idx
00: b075d6b8e93ad5b6dac45f20b429765015f8800b1db60b2709af3bd692d9c10b 7.419042107000 1012178 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": 578764, "vin": [ { "gen": { "height": 578754 } } ], "vout": [ { "amount": 7419042107, "target": { "key": "b075d6b8e93ad5b6dac45f20b429765015f8800b1db60b2709af3bd692d9c10b" } } ], "extra": [ 1, 129, 126, 2, 232, 26, 203, 22, 11, 45, 141, 136, 52, 34, 12, 66, 141, 177, 142, 54, 25, 216, 166, 13, 176, 170, 137, 249, 135, 216, 70, 239, 140, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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