Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34d9fcbf3dd2b6dbe17ef028e010d8721a682d0faa9006f76995e767eaffd888

Tx prefix hash: fc97115160e81c2e1292f291c38e357881e3bae2bda58d9a72ce371a63d23b04
Tx public key: e1a9ec30c7840fb6ae88a429ed9eb01c17dd19713c436efa958bb6c9718db065
Timestamp: 1742906456 Timestamp [UCT]: 2025-03-25 12:40:56 Age [y:d:h:m:s]: 00:254:09:20:52
Block: 1246977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179585 RingCT/type: yes/0
Extra: 01e1a9ec30c7840fb6ae88a429ed9eb01c17dd19713c436efa958bb6c9718db06502110000000124ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 284fca3549241a1bee1b2cd5a342fdcf8f0df58fe58d3cc5c0c24fc18dbf0c92 0.600000000000 1733978 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": 1246987, "vin": [ { "gen": { "height": 1246977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "284fca3549241a1bee1b2cd5a342fdcf8f0df58fe58d3cc5c0c24fc18dbf0c92" } } ], "extra": [ 1, 225, 169, 236, 48, 199, 132, 15, 182, 174, 136, 164, 41, 237, 158, 176, 28, 23, 221, 25, 113, 60, 67, 110, 250, 149, 139, 182, 201, 113, 141, 176, 101, 2, 17, 0, 0, 0, 1, 36, 255, 78, 161, 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