Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8aa592420de6262fa0019e289b35e90317caa9fe0532dba600840326eafd95a0

Tx prefix hash: 28f5e6a90cf716f4edd4487e926f9b32cbf67a2e529cf13a28d333ad3ca7c257
Tx public key: d9696af26f5016aefc73362f32bfbf7b06ea44f4d232a949bf7f7c510bc692d3
Timestamp: 1711112871 Timestamp [UCT]: 2024-03-22 13:07:51 Age [y:d:h:m:s]: 01:008:11:46:59
Block: 983899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267018 RingCT/type: yes/0
Extra: 01d9696af26f5016aefc73362f32bfbf7b06ea44f4d232a949bf7f7c510bc692d302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 879edd14e152b3b3cd5d256c0bf150945f0ee42a143ee00e3f43f1038739e5c9 0.600000000000 1444052 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": 983909, "vin": [ { "gen": { "height": 983899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "879edd14e152b3b3cd5d256c0bf150945f0ee42a143ee00e3f43f1038739e5c9" } } ], "extra": [ 1, 217, 105, 106, 242, 111, 80, 22, 174, 252, 115, 54, 47, 50, 191, 191, 123, 6, 234, 68, 244, 210, 50, 169, 73, 191, 127, 124, 81, 11, 198, 146, 211, 2, 17, 0, 0, 0, 3, 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