Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ec38231bac0c00d5895225bd06bbb4404f8c9c61061be2724508d10e83064b3

Tx prefix hash: e7d6f76a624092508a9d9fe4bb04157b9d7b480178f22f3a43de7ee0aa2de647
Tx public key: 8f627ce6e93050203df344c14f5b4fcceb57ad5dcffe3cb58005e228d517c496
Timestamp: 1736690284 Timestamp [UCT]: 2025-01-12 13:58:04 Age [y:d:h:m:s]: 00:064:17:47:42
Block: 1195786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46044 RingCT/type: yes/0
Extra: 018f627ce6e93050203df344c14f5b4fcceb57ad5dcffe3cb58005e228d517c4960211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b5b0cb73f1842a6e538c7bb5b32825f6678370ecff2013e21ae7ce0ff0ff5c4 0.600000000000 1682379 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": 1195796, "vin": [ { "gen": { "height": 1195786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b5b0cb73f1842a6e538c7bb5b32825f6678370ecff2013e21ae7ce0ff0ff5c4" } } ], "extra": [ 1, 143, 98, 124, 230, 233, 48, 80, 32, 61, 243, 68, 193, 79, 91, 79, 204, 235, 87, 173, 93, 207, 254, 60, 181, 128, 5, 226, 40, 213, 23, 196, 150, 2, 17, 0, 0, 0, 1, 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