Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33b9b2d7a10f4ce3fad16e54b32de9f03c09343d804865aec819fdbea498ac5

Tx prefix hash: cf58acf8beabc0978b471c38ef0f334f6c9b28385e5e5d0b7819459a2e68d5b3
Tx public key: 34bf210fd46b603612a2114127cb69d93a2692755848bfe9ce4e3351b415b61e
Timestamp: 1756574018 Timestamp [UCT]: 2025-08-30 17:13:38 Age [y:d:h:m:s]: 00:131:02:37:31
Block: 1357828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93730 RingCT/type: yes/0
Extra: 0134bf210fd46b603612a2114127cb69d93a2692755848bfe9ce4e3351b415b61e021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38ad69b250aadd09c8b0cbf4707d0c74ed527a56e3cf755c6fc0d22e19154f4f 0.600000000000 1845837 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": 1357838, "vin": [ { "gen": { "height": 1357828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38ad69b250aadd09c8b0cbf4707d0c74ed527a56e3cf755c6fc0d22e19154f4f" } } ], "extra": [ 1, 52, 191, 33, 15, 212, 107, 96, 54, 18, 162, 17, 65, 39, 203, 105, 217, 58, 38, 146, 117, 88, 72, 191, 233, 206, 78, 51, 81, 180, 21, 182, 30, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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