Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62c517750649b462ebf9b8d31d58ef4ea3fa03e0fabf48e703fb18201f80bd02

Tx prefix hash: 3246abbbf4dd56bedbb81d4df4cb01ac87a23f21357d0b726662b891089d5a1e
Tx public key: e55bca1866e7f90e2e67ca8fed88f0cde14f2327afd8747d884801dd1875b61e
Timestamp: 1755171699 Timestamp [UCT]: 2025-08-14 11:41:39 Age [y:d:h:m:s]: 00:052:11:31:25
Block: 1346643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36968 RingCT/type: yes/0
Extra: 01e55bca1866e7f90e2e67ca8fed88f0cde14f2327afd8747d884801dd1875b61e021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf529f44299d0d2c902a3062c4d5a5e58a65033b54d4db5db0199b73b3bfaba 0.600000000000 1834544 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": 1346653, "vin": [ { "gen": { "height": 1346643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf529f44299d0d2c902a3062c4d5a5e58a65033b54d4db5db0199b73b3bfaba" } } ], "extra": [ 1, 229, 91, 202, 24, 102, 231, 249, 14, 46, 103, 202, 143, 237, 136, 240, 205, 225, 79, 35, 39, 175, 216, 116, 125, 136, 72, 1, 221, 24, 117, 182, 30, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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