Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cca1ad7978095a075ee85db43b3affa8d5ee8a3832e1e50798c1e7b59d7a0fe0

Tx prefix hash: e355d0eb966d61dc931bd9ee55ff89146733dc392d28285c8942fd46db30bc61
Tx public key: d94da1f453a7ff0bfc23d9e7754db0a5a5c17dc0c1405056f61856ea477b4602
Timestamp: 1751202994 Timestamp [UCT]: 2025-06-29 13:16:34 Age [y:d:h:m:s]: 00:139:15:16:52
Block: 1315211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97928 RingCT/type: yes/0
Extra: 01d94da1f453a7ff0bfc23d9e7754db0a5a5c17dc0c1405056f61856ea477b4602021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f29ea4364ddcf68a6a646fdfcbb802fe6a72b618d009b5a8e8035bd84f33c60a 0.600000000000 1802864 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": 1315221, "vin": [ { "gen": { "height": 1315211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f29ea4364ddcf68a6a646fdfcbb802fe6a72b618d009b5a8e8035bd84f33c60a" } } ], "extra": [ 1, 217, 77, 161, 244, 83, 167, 255, 11, 252, 35, 217, 231, 117, 77, 176, 165, 165, 193, 125, 192, 193, 64, 80, 86, 246, 24, 86, 234, 71, 123, 70, 2, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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