Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ad72ed6a75c676879742b300c379c2af1adaf487d5d6b445516646e97a1d4e0

Tx prefix hash: 1e2dd357e6ed56fab002d65e4c737496c3300e4b928e4790373795efa38192b7
Tx public key: 3c604395b4142f5ff798f8d1ce5ebf9f84d7a971c1f5121bc69c153994bf28b9
Timestamp: 1680978055 Timestamp [UCT]: 2023-04-08 18:20:55 Age [y:d:h:m:s]: 01:275:21:03:05
Block: 734337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458618 RingCT/type: yes/0
Extra: 013c604395b4142f5ff798f8d1ce5ebf9f84d7a971c1f5121bc69c153994bf28b90211000000035029cbac000000000000000000

1 output(s) for total of 2.263794014000 dcy

stealth address amount amount idx
00: abf05fb3f17bb1f8344d9e18e72db35b42e6499a545b21b7f319edcd00e2a922 2.263794014000 1180526 of 0

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": 734347, "vin": [ { "gen": { "height": 734337 } } ], "vout": [ { "amount": 2263794014, "target": { "key": "abf05fb3f17bb1f8344d9e18e72db35b42e6499a545b21b7f319edcd00e2a922" } } ], "extra": [ 1, 60, 96, 67, 149, 180, 20, 47, 95, 247, 152, 248, 209, 206, 94, 191, 159, 132, 215, 169, 113, 193, 245, 18, 27, 198, 156, 21, 57, 148, 191, 40, 185, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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