Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7531ae4107e6e9f8d76af938601e12547882a1685046b6e77d7074f5bba24a10

Tx prefix hash: 2c3d339691e46e278b833ddddffeb21036d4c199772ba61d71c5df8792b5a446
Tx public key: 7111a23c12688c379e8e1518d1dc16f14ace33b44e820a7b9f0e4af72278fd1d
Timestamp: 1723909632 Timestamp [UCT]: 2024-08-17 15:47:12 Age [y:d:h:m:s]: 00:227:11:22:55
Block: 1089974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162427 RingCT/type: yes/0
Extra: 017111a23c12688c379e8e1518d1dc16f14ace33b44e820a7b9f0e4af72278fd1d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2660f1061938f63ccffc53a2de1aaf4fa25065e8a8b9089b0e062a8b9464512d 0.600000000000 1564597 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": 1089984, "vin": [ { "gen": { "height": 1089974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2660f1061938f63ccffc53a2de1aaf4fa25065e8a8b9089b0e062a8b9464512d" } } ], "extra": [ 1, 113, 17, 162, 60, 18, 104, 140, 55, 158, 142, 21, 24, 209, 220, 22, 241, 74, 206, 51, 180, 78, 130, 10, 123, 159, 14, 74, 247, 34, 120, 253, 29, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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