Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7d42c6dc0a89e85ab140c5b6f18b76c0110f651875a354987f22bff599035a0

Tx prefix hash: f568743f48e35b7afad3887a37f88d0101050980b174811e6ade426931a7ec74
Tx public key: eda8f18b8e175a92dd7a0796a056a33abfca307345733be27c625702851c782f
Timestamp: 1734738747 Timestamp [UCT]: 2024-12-20 23:52:27 Age [y:d:h:m:s]: 00:328:14:39:36
Block: 1179656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232353 RingCT/type: yes/0
Extra: 01eda8f18b8e175a92dd7a0796a056a33abfca307345733be27c625702851c782f0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5540d46ea3f733094a8d79f88df9f88e5d47f86152e0c5e63cc70614d0e144a 0.600000000000 1666055 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": 1179666, "vin": [ { "gen": { "height": 1179656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5540d46ea3f733094a8d79f88df9f88e5d47f86152e0c5e63cc70614d0e144a" } } ], "extra": [ 1, 237, 168, 241, 139, 142, 23, 90, 146, 221, 122, 7, 150, 160, 86, 163, 58, 191, 202, 48, 115, 69, 115, 59, 226, 124, 98, 87, 2, 133, 28, 120, 47, 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