Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39a6e031684db095479c2eb5662274cc8af5844a2f99cddf9d54968b50b25e15

Tx prefix hash: d25670f752380b447eb1fa07899c074d62dd6653c2662ef7a69ca6939e142d72
Tx public key: 8482fbe0e9957ab1dad5aef973323a7c52005ba5a53c4f86430cb2a5f4119b3d
Timestamp: 1749437782 Timestamp [UCT]: 2025-06-09 02:56:22 Age [y:d:h:m:s]: 00:158:20:40:44
Block: 1301056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111219 RingCT/type: yes/0
Extra: 018482fbe0e9957ab1dad5aef973323a7c52005ba5a53c4f86430cb2a5f4119b3d021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d730c852de8e2e2ef73b1338753e48070f1c6ae3dc46ae6b7670e48b0909bccb 0.600000000000 1788609 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": 1301066, "vin": [ { "gen": { "height": 1301056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d730c852de8e2e2ef73b1338753e48070f1c6ae3dc46ae6b7670e48b0909bccb" } } ], "extra": [ 1, 132, 130, 251, 224, 233, 149, 122, 177, 218, 213, 174, 249, 115, 50, 58, 124, 82, 0, 91, 165, 165, 60, 79, 134, 67, 12, 178, 165, 244, 17, 155, 61, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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