Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3bbe5b1209b2f4adca37a040f6f6c2e13ff150c4266d68975b0169c91582698

Tx prefix hash: 31671e4a4c3f224e1bd1b8fdb78fa1fd225312f551565a247cde0b7eb30e6d86
Tx public key: 750a0026ea25c8af75e5a58907f0d3f52fe36db01617f72c2bb801e93d804cd3
Timestamp: 1751049121 Timestamp [UCT]: 2025-06-27 18:32:01 Age [y:d:h:m:s]: 00:195:01:19:08
Block: 1314036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137521 RingCT/type: yes/0
Extra: 01750a0026ea25c8af75e5a58907f0d3f52fe36db01617f72c2bb801e93d804cd30211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c57531495c8e9edadc8a0044b8377fdb1b6ddc49d80ebd478389fafe114e7aa 0.600000000000 1801681 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": 1314046, "vin": [ { "gen": { "height": 1314036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c57531495c8e9edadc8a0044b8377fdb1b6ddc49d80ebd478389fafe114e7aa" } } ], "extra": [ 1, 117, 10, 0, 38, 234, 37, 200, 175, 117, 229, 165, 137, 7, 240, 211, 245, 47, 227, 109, 176, 22, 23, 247, 44, 43, 184, 1, 233, 61, 128, 76, 211, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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