Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df010a462b411c56f9708adf6a8793a9ce6102a1ed91e1b4eb5f041e9cf0d3f

Tx prefix hash: 655af9e493ceff95ef9c0e4949433dca9e311a5bd8a3959dbb815a86b2fe1507
Tx public key: c55c4681a4620fdedd3ddbbc1acf0df2d3f4fbb2581970d4d647449d4e67cfc3
Timestamp: 1705236611 Timestamp [UCT]: 2024-01-14 12:50:11 Age [y:d:h:m:s]: 01:300:06:52:33
Block: 935149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473434 RingCT/type: yes/0
Extra: 01c55c4681a4620fdedd3ddbbc1acf0df2d3f4fbb2581970d4d647449d4e67cfc30211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edca10701a9847d5bdad6b67261f215f80cc6df37e9d0e6ef1ac7afb0e91676b 0.600000000000 1393165 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": 935159, "vin": [ { "gen": { "height": 935149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edca10701a9847d5bdad6b67261f215f80cc6df37e9d0e6ef1ac7afb0e91676b" } } ], "extra": [ 1, 197, 92, 70, 129, 164, 98, 15, 222, 221, 61, 219, 188, 26, 207, 13, 242, 211, 244, 251, 178, 88, 25, 112, 212, 214, 71, 68, 157, 78, 103, 207, 195, 2, 17, 0, 0, 0, 8, 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