Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38083c321fcf42b91c56fab718d2b6d2a1a04e6d32caccf409090b09735027b

Tx prefix hash: 10146ad1aeb38a23ea0d2093432d583b1a961ab792d3ed543ec97e5914b4dd0e
Tx public key: 5346e6f2998ca9d9400d110bd74e41d045326b768c7fd677a28498a2f49cc622
Timestamp: 1711993814 Timestamp [UCT]: 2024-04-01 17:50:14 Age [y:d:h:m:s]: 01:043:23:33:32
Block: 991149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292447 RingCT/type: yes/0
Extra: 015346e6f2998ca9d9400d110bd74e41d045326b768c7fd677a28498a2f49cc6220211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844c2c3ee0e9b2cfa782d1540af93a75bc0f9431c9e8ae847680d007a1f32b70 0.600000000000 1451483 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": 991159, "vin": [ { "gen": { "height": 991149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844c2c3ee0e9b2cfa782d1540af93a75bc0f9431c9e8ae847680d007a1f32b70" } } ], "extra": [ 1, 83, 70, 230, 242, 153, 140, 169, 217, 64, 13, 17, 11, 215, 78, 65, 208, 69, 50, 107, 118, 140, 127, 214, 119, 162, 132, 152, 162, 244, 156, 198, 34, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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