Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14ae9a2b72ccf87c3625db5c16f8942b9a090d47b1aed7d327276cdbabf9c47

Tx prefix hash: af35c9e52bbb675752e27a6c9d60a763d5b1c87c6ccaf633af3ebb93154ee73e
Tx public key: d0529e72e766cbac6d377ce70f3446f6a075f8ba38f66a93bce79c0f64f5982f
Timestamp: 1711115746 Timestamp [UCT]: 2024-03-22 13:55:46 Age [y:d:h:m:s]: 00:361:21:10:04
Block: 983923 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258739 RingCT/type: yes/0
Extra: 01d0529e72e766cbac6d377ce70f3446f6a075f8ba38f66a93bce79c0f64f5982f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23ca004fb9ab0852183d714126fa9164c38a7ab8aaaba5561ae813a11fa80689 0.600000000000 1444076 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": 983933, "vin": [ { "gen": { "height": 983923 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23ca004fb9ab0852183d714126fa9164c38a7ab8aaaba5561ae813a11fa80689" } } ], "extra": [ 1, 208, 82, 158, 114, 231, 102, 203, 172, 109, 55, 124, 231, 15, 52, 70, 246, 160, 117, 248, 186, 56, 246, 106, 147, 188, 231, 156, 15, 100, 245, 152, 47, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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