Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 867a535ed577f295677f3eaa0f21159d838de87cdf9fe249e31b7bff6352cb1a

Tx prefix hash: 3662badf4710b82bc50ac398ebfc14309576b1edbe2e31bdf9718d81343b30e8
Tx public key: 7c53919f556012be683bf76d1c3d4e6a7637ce1a4a16873ff0c8c7df6af6873c
Timestamp: 1751011480 Timestamp [UCT]: 2025-06-27 08:04:40 Age [y:d:h:m:s]: 00:147:10:22:00
Block: 1313734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103394 RingCT/type: yes/0
Extra: 017c53919f556012be683bf76d1c3d4e6a7637ce1a4a16873ff0c8c7df6af6873c021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce887b9e46fdaceea6d4bc743d744cc08f9d38b2e257133933d759caa4ad6971 0.600000000000 1801377 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": 1313744, "vin": [ { "gen": { "height": 1313734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce887b9e46fdaceea6d4bc743d744cc08f9d38b2e257133933d759caa4ad6971" } } ], "extra": [ 1, 124, 83, 145, 159, 85, 96, 18, 190, 104, 59, 247, 109, 28, 61, 78, 106, 118, 55, 206, 26, 74, 22, 135, 63, 240, 200, 199, 223, 106, 246, 135, 60, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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