Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ab61a40950d1d96b9eade30f83fb4cad4e68d770a6a88799fbf7e2929e57bf

Tx prefix hash: 510f396849b6fd52817107bcbcace4e15542982e34a4170b7fe1602b3d63ef7a
Tx public key: 33a02728253f7870d076ae00b2017b514668e7fcc9c8d24ee16cf56de6f2cb71
Timestamp: 1714421150 Timestamp [UCT]: 2024-04-29 20:05:50 Age [y:d:h:m:s]: 00:198:13:35:09
Block: 1011301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142140 RingCT/type: yes/0
Extra: 0133a02728253f7870d076ae00b2017b514668e7fcc9c8d24ee16cf56de6f2cb710211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee33a3d74c375e49e022f7e7daa9f8b453f118c0ee9b18dcc6033e445594675c 0.600000000000 1473495 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": 1011311, "vin": [ { "gen": { "height": 1011301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee33a3d74c375e49e022f7e7daa9f8b453f118c0ee9b18dcc6033e445594675c" } } ], "extra": [ 1, 51, 160, 39, 40, 37, 63, 120, 112, 208, 118, 174, 0, 178, 1, 123, 81, 70, 104, 231, 252, 201, 200, 210, 78, 225, 108, 245, 109, 230, 242, 203, 113, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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