Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 824dc6053013de84b9d78d9d66e13c736c1afd4425efdfd6bfe0a7487e7baeed

Tx prefix hash: 8371d6ee64de80bc12394a238e188f0081e728fdb793d4ab7d166e933d430355
Tx public key: 64c376cf2c990f3ab8038c2b8932dc0d2cd31d17e2e471dffb741557f8718484
Timestamp: 1707905844 Timestamp [UCT]: 2024-02-14 10:17:24 Age [y:d:h:m:s]: 01:043:00:18:11
Block: 957279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291785 RingCT/type: yes/0
Extra: 0164c376cf2c990f3ab8038c2b8932dc0d2cd31d17e2e471dffb741557f87184840211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: baf8b09ab1c5fe4043ba385b918cfcaa325f49b42e7af34054f271f0e75a7dc5 0.600000000000 1416595 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": 957289, "vin": [ { "gen": { "height": 957279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baf8b09ab1c5fe4043ba385b918cfcaa325f49b42e7af34054f271f0e75a7dc5" } } ], "extra": [ 1, 100, 195, 118, 207, 44, 153, 15, 58, 184, 3, 140, 43, 137, 50, 220, 13, 44, 211, 29, 23, 226, 228, 113, 223, 251, 116, 21, 87, 248, 113, 132, 132, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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