Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9b24a33e4a2452d389a6fd68a8b7e4909af0ac473544d006c3cf8565f4bbf8f

Tx prefix hash: bded08f594d9ed76d91e48432a501ccd98dcf580ad21dc266b7ff892f462ae26
Tx public key: dee18fb8f3d6e89956d924941f820980add2a7561ad13366a5c1cfdf190862a5
Timestamp: 1708846837 Timestamp [UCT]: 2024-02-25 07:40:37 Age [y:d:h:m:s]: 01:282:13:15:39
Block: 965096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460712 RingCT/type: yes/0
Extra: 01dee18fb8f3d6e89956d924941f820980add2a7561ad13366a5c1cfdf190862a502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6006116554cccb3bfe9dad436c9af1953de3074c455fffc5975d0048e3e60ee9 0.600000000000 1424845 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": 965106, "vin": [ { "gen": { "height": 965096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6006116554cccb3bfe9dad436c9af1953de3074c455fffc5975d0048e3e60ee9" } } ], "extra": [ 1, 222, 225, 143, 184, 243, 214, 232, 153, 86, 217, 36, 148, 31, 130, 9, 128, 173, 210, 167, 86, 26, 209, 51, 102, 165, 193, 207, 223, 25, 8, 98, 165, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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