Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c9088eac53c7b0ea3ed1198839b6b9524471f7a22d427f7a5931657c4aeac1

Tx prefix hash: e5d4df193ee844663d64250d0a5ff662f731c372180bce3306f20b64fab4cbb5
Tx public key: 6c9c4eb284bd1722443805f76fd3ac5380fdff4e4da78f12118ce43273518711
Timestamp: 1752656904 Timestamp [UCT]: 2025-07-16 09:08:24 Age [y:d:h:m:s]: 00:120:23:42:06
Block: 1326624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85214 RingCT/type: yes/0
Extra: 016c9c4eb284bd1722443805f76fd3ac5380fdff4e4da78f12118ce43273518711021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7543184664c90251a5f621c9fa59de417c29e90aaea276c80cc8d9d69a9540f9 0.600000000000 1814375 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": 1326634, "vin": [ { "gen": { "height": 1326624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7543184664c90251a5f621c9fa59de417c29e90aaea276c80cc8d9d69a9540f9" } } ], "extra": [ 1, 108, 156, 78, 178, 132, 189, 23, 34, 68, 56, 5, 247, 111, 211, 172, 83, 128, 253, 255, 78, 77, 167, 143, 18, 17, 140, 228, 50, 115, 81, 135, 17, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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