Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9937a163409b3bf728f1b09ce2e2d6502abc49d8e80b1aee8c1763ef7405c641

Tx prefix hash: ddef3fbab94c0db3fa417558a8c86cd81110312bbb2ba64a7c945556e1f3590a
Tx public key: a2e02fc4c7189bb6414b67e7990c6c678bb9ec8cc06ddb2097a01c53d2a3bfe1
Timestamp: 1763849819 Timestamp [UCT]: 2025-11-22 22:16:59 Age [y:d:h:m:s]: 00:031:00:32:33
Block: 1417960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22204 RingCT/type: yes/0
Extra: 01a2e02fc4c7189bb6414b67e7990c6c678bb9ec8cc06ddb2097a01c53d2a3bfe1021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7978fe3875ad878e2364a8598929f19ddd2bfd38b921f5b2649beae89944d0aa 0.600000000000 1906487 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": 1417970, "vin": [ { "gen": { "height": 1417960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7978fe3875ad878e2364a8598929f19ddd2bfd38b921f5b2649beae89944d0aa" } } ], "extra": [ 1, 162, 224, 47, 196, 199, 24, 155, 182, 65, 75, 103, 231, 153, 12, 108, 103, 139, 185, 236, 140, 192, 109, 219, 32, 151, 160, 28, 83, 210, 163, 191, 225, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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