Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d81b62826babcd21f26db84d89ab1e69dedd7d05ea9380285150cd99751283

Tx prefix hash: 3adfb9349bbf02b927f608267e863b467f03e0cb60c81e6edc03e3a54ac5b0eb
Tx public key: 36dd02c030d1d5e0007935e3e5738b1cb5910b05beb2b558aa765c09f588912d
Timestamp: 1755033162 Timestamp [UCT]: 2025-08-12 21:12:42 Age [y:d:h:m:s]: 00:105:18:25:59
Block: 1345684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74948 RingCT/type: yes/0
Extra: 0136dd02c030d1d5e0007935e3e5738b1cb5910b05beb2b558aa765c09f588912d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a20faa1546ff167b8bf409cbcbf5e45246c3639cabf954b7dae6721c67e68ef3 0.600000000000 1833579 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": 1345694, "vin": [ { "gen": { "height": 1345684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a20faa1546ff167b8bf409cbcbf5e45246c3639cabf954b7dae6721c67e68ef3" } } ], "extra": [ 1, 54, 221, 2, 192, 48, 209, 213, 224, 0, 121, 53, 227, 229, 115, 139, 28, 181, 145, 11, 5, 190, 178, 181, 88, 170, 118, 92, 9, 245, 136, 145, 45, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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