Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11524f0283c9eb33a35b22b2b39543e10111361a4f254af81c3be4e4aa21e351

Tx prefix hash: c81c7112267f549a89dfd11d4dfbfbbdf7f32fa5040f6355fff57c9a8ba8f54d
Tx public key: 0ab5ef084902a6e65218abdae554f16c90d6bb1bc67b91e6deb871d63bf83021
Timestamp: 1751669424 Timestamp [UCT]: 2025-07-04 22:50:24 Age [y:d:h:m:s]: 00:131:13:31:30
Block: 1318896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92330 RingCT/type: yes/0
Extra: 010ab5ef084902a6e65218abdae554f16c90d6bb1bc67b91e6deb871d63bf83021021100000011bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c45f8020ebf2aedaebd33790f0f9fa7b41b58c24ac8b8a9904b7b3a7bc44821 0.600000000000 1806583 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": 1318906, "vin": [ { "gen": { "height": 1318896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c45f8020ebf2aedaebd33790f0f9fa7b41b58c24ac8b8a9904b7b3a7bc44821" } } ], "extra": [ 1, 10, 181, 239, 8, 73, 2, 166, 230, 82, 24, 171, 218, 229, 84, 241, 108, 144, 214, 187, 27, 198, 123, 145, 230, 222, 184, 113, 214, 59, 248, 48, 33, 2, 17, 0, 0, 0, 17, 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