Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8d84a186be578845af71fd1cfabd27d4ba5284e8af9016e5b9d9b4535b8da48

Tx prefix hash: 33588b43f265edc899f0e08e095c2e295467f2aec253a8f2a3d89ea9b9627b98
Tx public key: 17a209b8a4a813ab30a8d3f8fb58e78b6d341c85eccd2cdaa9c25cee8db72fa9
Timestamp: 1714932607 Timestamp [UCT]: 2024-05-05 18:10:07 Age [y:d:h:m:s]: 00:207:01:20:32
Block: 1015551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148209 RingCT/type: yes/0
Extra: 0117a209b8a4a813ab30a8d3f8fb58e78b6d341c85eccd2cdaa9c25cee8db72fa90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d4274f6f63b3527bb121b84970d3307be30c202dbbfada0dbbf35d72693f12e 0.600000000000 1478950 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": 1015561, "vin": [ { "gen": { "height": 1015551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d4274f6f63b3527bb121b84970d3307be30c202dbbfada0dbbf35d72693f12e" } } ], "extra": [ 1, 23, 162, 9, 184, 164, 168, 19, 171, 48, 168, 211, 248, 251, 88, 231, 139, 109, 52, 28, 133, 236, 205, 44, 218, 169, 194, 92, 238, 141, 183, 47, 169, 2, 17, 0, 0, 0, 3, 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