Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f10874c913aedf152d10a38b1e55e792b296af38eb3f4c071fb9a8bad14179

Tx prefix hash: 0b7ea9d4f6898746c3192243050398c09007136a4bf9fde8d9ddd916d34316f2
Tx public key: a6131de83fed0f5d7cb98eaf4017a211efa97f9d143fc29f77d25156d35e956d
Timestamp: 1751552736 Timestamp [UCT]: 2025-07-03 14:25:36 Age [y:d:h:m:s]: 00:130:08:57:02
Block: 1318003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91400 RingCT/type: yes/0
Extra: 01a6131de83fed0f5d7cb98eaf4017a211efa97f9d143fc29f77d25156d35e956d021100000012bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ab52d4081c905ea75e7779dd9f73635128ed40dd8e457b3efe66d9dd6caf6ac 0.600000000000 1805674 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": 1318013, "vin": [ { "gen": { "height": 1318003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ab52d4081c905ea75e7779dd9f73635128ed40dd8e457b3efe66d9dd6caf6ac" } } ], "extra": [ 1, 166, 19, 29, 232, 63, 237, 15, 93, 124, 185, 142, 175, 64, 23, 162, 17, 239, 169, 127, 157, 20, 63, 194, 159, 119, 210, 81, 86, 211, 94, 149, 109, 2, 17, 0, 0, 0, 18, 191, 81, 178, 162, 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