Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de206f331be683352db6fe0b30605a3fd3c01e3e6c9ab50d540b250b510b3ee4

Tx prefix hash: 815559595857d17ee8e114fc2ca5db04b4033720b7d0f377bbb541c06902a482
Tx public key: f631e9eadaf6d28625a71ba2c3d2dca5a739a3685c323df0a767a3ab2a061b9f
Timestamp: 1750801576 Timestamp [UCT]: 2025-06-24 21:46:16 Age [y:d:h:m:s]: 00:149:23:30:53
Block: 1312088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105126 RingCT/type: yes/0
Extra: 01f631e9eadaf6d28625a71ba2c3d2dca5a739a3685c323df0a767a3ab2a061b9f02110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c5dd7d566e1362d7fb2944ba8b443491316a302419f619ed1ec1806385b43dc 0.600000000000 1799719 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": 1312098, "vin": [ { "gen": { "height": 1312088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c5dd7d566e1362d7fb2944ba8b443491316a302419f619ed1ec1806385b43dc" } } ], "extra": [ 1, 246, 49, 233, 234, 218, 246, 210, 134, 37, 167, 27, 162, 195, 210, 220, 165, 167, 57, 163, 104, 92, 50, 61, 240, 167, 103, 163, 171, 42, 6, 27, 159, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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