Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e634dc9fd029c077b6dafe21eba64110e510eeaf6c5ddc1107f0326f72ada8ad

Tx prefix hash: d59245fde95fbdf742d32be23d33afad42d69d650e86ad110f0d1f7f07912702
Tx public key: b7063378fea7e61079ab154e8fbcb4c85cc116438c99d309aa9c847ed1fefb8c
Timestamp: 1736976947 Timestamp [UCT]: 2025-01-15 21:35:47 Age [y:d:h:m:s]: 00:309:01:46:25
Block: 1198149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218407 RingCT/type: yes/0
Extra: 01b7063378fea7e61079ab154e8fbcb4c85cc116438c99d309aa9c847ed1fefb8c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e983853c531fff383966b3d4375166671afdf2e610e49cfbe9b00e772b6eec3 0.600000000000 1684768 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": 1198159, "vin": [ { "gen": { "height": 1198149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e983853c531fff383966b3d4375166671afdf2e610e49cfbe9b00e772b6eec3" } } ], "extra": [ 1, 183, 6, 51, 120, 254, 167, 230, 16, 121, 171, 21, 78, 143, 188, 180, 200, 92, 193, 22, 67, 140, 153, 211, 9, 170, 156, 132, 126, 209, 254, 251, 140, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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