Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e3d0ae0f85335dc15a3a7707480dee47c8dfcce3e2dec22252d72a6b241864

Tx prefix hash: 65c323eb78dddd41b52151ecbba4d9666116a6f1acf40bf3e848036a8a8e3691
Tx public key: cf783f66660b6bd1694716f370e50614c3c4dc0a002f257a6ad339bfdb524db3
Timestamp: 1752506619 Timestamp [UCT]: 2025-07-14 15:23:39 Age [y:d:h:m:s]: 00:129:10:15:04
Block: 1325392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91226 RingCT/type: yes/0
Extra: 01cf783f66660b6bd1694716f370e50614c3c4dc0a002f257a6ad339bfdb524db30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4970c98aad8f1c8e70a17272425a8d1b094ffef24bb61144515504ebdbe2f7a9 0.600000000000 1813137 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": 1325402, "vin": [ { "gen": { "height": 1325392 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4970c98aad8f1c8e70a17272425a8d1b094ffef24bb61144515504ebdbe2f7a9" } } ], "extra": [ 1, 207, 120, 63, 102, 102, 11, 107, 209, 105, 71, 22, 243, 112, 229, 6, 20, 195, 196, 220, 10, 0, 47, 37, 122, 106, 211, 57, 191, 219, 82, 77, 179, 2, 17, 0, 0, 0, 1, 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