Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c007315e3cae213117c013753279f14d08a2bc8413a62ac3b962fab1aead0ec3

Tx prefix hash: a8369c4d985328ca14d5e647e8a2d88b47a845de3c48ce0000234101e034fab7
Tx public key: 39e9a2ba8cd6fcfbfd5fb7686485c8bae1e6ba0875119e9c756d0a5f53570ed1
Timestamp: 1709029323 Timestamp [UCT]: 2024-02-27 10:22:03 Age [y:d:h:m:s]: 00:364:13:41:21
Block: 966611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260664 RingCT/type: yes/0
Extra: 0139e9a2ba8cd6fcfbfd5fb7686485c8bae1e6ba0875119e9c756d0a5f53570ed10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 520784a8df2c00eb5c823285622be047f7a1c4031afd1cdd3b4e9b7a5de0dd17 0.600000000000 1426374 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": 966621, "vin": [ { "gen": { "height": 966611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "520784a8df2c00eb5c823285622be047f7a1c4031afd1cdd3b4e9b7a5de0dd17" } } ], "extra": [ 1, 57, 233, 162, 186, 140, 214, 252, 251, 253, 95, 183, 104, 100, 133, 200, 186, 225, 230, 186, 8, 117, 17, 158, 156, 117, 109, 10, 95, 83, 87, 14, 209, 2, 17, 0, 0, 0, 4, 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