Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ea96ac941b14887b9200a7cf7da73ba40bda6ae1e3f1bd6577aa144c57af46

Tx prefix hash: 2f57494b9a304eb30b58711474f2f80573495f81578d4fc0a585180eedbbf6d8
Tx public key: 21ccfa3a82dccf85f6489e5e199680a308abc4c8d319f12e9ae2c319739b2055
Timestamp: 1754622182 Timestamp [UCT]: 2025-08-08 03:03:02 Age [y:d:h:m:s]: 00:053:16:20:49
Block: 1342541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37376 RingCT/type: yes/0
Extra: 0121ccfa3a82dccf85f6489e5e199680a308abc4c8d319f12e9ae2c319739b205502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c3d05eb7aa83a2cacd8ebf8d6e735083d679fddced94e3300deeb64557d9ef5 0.600000000000 1830374 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": 1342551, "vin": [ { "gen": { "height": 1342541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c3d05eb7aa83a2cacd8ebf8d6e735083d679fddced94e3300deeb64557d9ef5" } } ], "extra": [ 1, 33, 204, 250, 58, 130, 220, 207, 133, 246, 72, 158, 94, 25, 150, 128, 163, 8, 171, 196, 200, 211, 25, 241, 46, 154, 226, 195, 25, 115, 155, 32, 85, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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