Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec0440b0ac5a3e202e487bed5e3bab47fc853f5db037f6221f8f16b64fe53a8

Tx prefix hash: a2c7bf52ba3036716673b4e1b07db112f56e45f78fdec9f0bfdeea814586588c
Tx public key: 71a4e8dccc4e316fe52f8dce3e00fbe4950c1935c467f50dc3ca00dcf2e5728e
Timestamp: 1700704362 Timestamp [UCT]: 2023-11-23 01:52:42 Age [y:d:h:m:s]: 01:131:00:37:16
Block: 897580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354803 RingCT/type: yes/0
Extra: 0171a4e8dccc4e316fe52f8dce3e00fbe4950c1935c467f50dc3ca00dcf2e5728e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.651545641000 dcy

stealth address amount amount idx
00: b1d9edfde785e87e58eff4656bfdc0a37cae6d0fd3c49839087f955f626aba45 0.651545641000 1353961 of 0

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": 897590, "vin": [ { "gen": { "height": 897580 } } ], "vout": [ { "amount": 651545641, "target": { "key": "b1d9edfde785e87e58eff4656bfdc0a37cae6d0fd3c49839087f955f626aba45" } } ], "extra": [ 1, 113, 164, 232, 220, 204, 78, 49, 111, 229, 47, 141, 206, 62, 0, 251, 228, 149, 12, 25, 53, 196, 103, 245, 13, 195, 202, 0, 220, 242, 229, 114, 142, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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