Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e354ab2a0096a79958812bcaa544797700e72509aee654fdd4d3ee8d5113818

Tx prefix hash: fbad46c98133eecb97a4f3dc771dedfc0e08e704d2bb1a299ff18070bc2a0318
Tx public key: d5f74a08a517a3df79f01dca3fb6cf2460240dd9e5ee8e8a71192c3d6437b338
Timestamp: 1714493565 Timestamp [UCT]: 2024-04-30 16:12:45 Age [y:d:h:m:s]: 00:251:23:59:38
Block: 1011902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180373 RingCT/type: yes/0
Extra: 01d5f74a08a517a3df79f01dca3fb6cf2460240dd9e5ee8e8a71192c3d6437b33802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cafecb964d3ac4fee0531c48e016397f9ea64f91eccc78ca289815a41c858ede 0.600000000000 1474260 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": 1011912, "vin": [ { "gen": { "height": 1011902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cafecb964d3ac4fee0531c48e016397f9ea64f91eccc78ca289815a41c858ede" } } ], "extra": [ 1, 213, 247, 74, 8, 165, 23, 163, 223, 121, 240, 29, 202, 63, 182, 207, 36, 96, 36, 13, 217, 229, 238, 142, 138, 113, 25, 44, 61, 100, 55, 179, 56, 2, 17, 0, 0, 0, 1, 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