Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f02c56cece4e7b3bd39df377e5ebb483911803c32496e151d84ae8f01197e13

Tx prefix hash: 7e4e2a5f41baae8b7135fdb70a601dc23473b71d986bfdf9102674bdf5a5347c
Tx public key: b951398689600ec4104c451584ef85e4854fd3a69f782c3219c455f5b93626bf
Timestamp: 1754900046 Timestamp [UCT]: 2025-08-11 08:14:06 Age [y:d:h:m:s]: 00:108:21:41:17
Block: 1344675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77097 RingCT/type: yes/0
Extra: 01b951398689600ec4104c451584ef85e4854fd3a69f782c3219c455f5b93626bf021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36bf83e88ea2222d773cbc6a87cb0283d3cb737cae02b5b45a1f3f9d9684a025 0.600000000000 1832560 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": 1344685, "vin": [ { "gen": { "height": 1344675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36bf83e88ea2222d773cbc6a87cb0283d3cb737cae02b5b45a1f3f9d9684a025" } } ], "extra": [ 1, 185, 81, 57, 134, 137, 96, 14, 196, 16, 76, 69, 21, 132, 239, 133, 228, 133, 79, 211, 166, 159, 120, 44, 50, 25, 196, 85, 245, 185, 54, 38, 191, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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