Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d37f324a1cfa902f29874b0dc248747def753f41df59c688a8f44cecda57fa7c

Tx prefix hash: 1fe3a0c500c635577b276c5dad433ffe342cf6bd7fef2beb581bc7444767e611
Tx public key: 551ec8b4a037f8c3c926d3b7912d69a547efbce6e7376cb79ee33c3e59d2394e
Timestamp: 1763392833 Timestamp [UCT]: 2025-11-17 15:20:33 Age [y:d:h:m:s]: 00:035:17:20:18
Block: 1414178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25580 RingCT/type: yes/0
Extra: 01551ec8b4a037f8c3c926d3b7912d69a547efbce6e7376cb79ee33c3e59d2394e02110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a14e8d9221d12c679581cd3f93ca4f4f792c276cfa2b6d6d34b60f6abef06f36 0.600000000000 1902665 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": 1414188, "vin": [ { "gen": { "height": 1414178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a14e8d9221d12c679581cd3f93ca4f4f792c276cfa2b6d6d34b60f6abef06f36" } } ], "extra": [ 1, 85, 30, 200, 180, 160, 55, 248, 195, 201, 38, 211, 183, 145, 45, 105, 165, 71, 239, 188, 230, 231, 55, 108, 183, 158, 227, 60, 62, 89, 210, 57, 78, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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