Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d54ddb6c46651999824d9304a8f03d8ad751c5acac7b7447531ae6faaff8ca

Tx prefix hash: 40e7ec571da17e7ffcef4dc24f59407d872dc121d66d07037adcb377ae575210
Tx public key: ec2548e6c6d8ef8773fd9c744e680c0bb21fd5d4a65073c7f48057d0cb4a2982
Timestamp: 1756226307 Timestamp [UCT]: 2025-08-26 16:38:27 Age [y:d:h:m:s]: 00:093:16:54:21
Block: 1354966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66918 RingCT/type: yes/0
Extra: 01ec2548e6c6d8ef8773fd9c744e680c0bb21fd5d4a65073c7f48057d0cb4a29820211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31123a04e1d227efa6450384024cd76aaa700052b17a70b17f8db59327b6447a 0.600000000000 1842961 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": 1354976, "vin": [ { "gen": { "height": 1354966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31123a04e1d227efa6450384024cd76aaa700052b17a70b17f8db59327b6447a" } } ], "extra": [ 1, 236, 37, 72, 230, 198, 216, 239, 135, 115, 253, 156, 116, 78, 104, 12, 11, 178, 31, 213, 212, 166, 80, 115, 199, 244, 128, 87, 208, 203, 74, 41, 130, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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