Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00c8e17c4d48e93f3ee853af9bed4c789c6662ae6968093f90eb8c7d9ef28df0

Tx prefix hash: 7cfd6c70e9b137507ca365da8a2f38a09e20f7ee0e74ea8293a0dfac60114cf9
Tx public key: 003f0a37d4aaef6fb31d4d60b78d4fd03c4e3d2cc300979767a862459c8e17d0
Timestamp: 1711162306 Timestamp [UCT]: 2024-03-23 02:51:46 Age [y:d:h:m:s]: 01:061:04:27:15
Block: 984303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304739 RingCT/type: yes/0
Extra: 01003f0a37d4aaef6fb31d4d60b78d4fd03c4e3d2cc300979767a862459c8e17d00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 072f5926df7d5a66c1554d69124f33c0bc33009da1f430df351e12bc087b3ab0 0.600000000000 1444472 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": 984313, "vin": [ { "gen": { "height": 984303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "072f5926df7d5a66c1554d69124f33c0bc33009da1f430df351e12bc087b3ab0" } } ], "extra": [ 1, 0, 63, 10, 55, 212, 170, 239, 111, 179, 29, 77, 96, 183, 141, 79, 208, 60, 78, 61, 44, 195, 0, 151, 151, 103, 168, 98, 69, 156, 142, 23, 208, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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