Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ae1b60089c4485d8292ec49d560920cb528fc583014a028b23a6707fa4028f5

Tx prefix hash: 2c1ed04b8c95e9d5fe74eaabbbcd15457a9019638d0cbdbf726df9c5fa6e31a9
Tx public key: deec35d4a524dc06a38ad9e58eddf047c8566c3560317dc79d6483de4c3a1eba
Timestamp: 1707582947 Timestamp [UCT]: 2024-02-10 16:35:47 Age [y:d:h:m:s]: 01:008:09:12:58
Block: 954610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266981 RingCT/type: yes/0
Extra: 01deec35d4a524dc06a38ad9e58eddf047c8566c3560317dc79d6483de4c3a1eba0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019387e3c82ede269a15e99ddba0a95d06cc839ff6de9465df310d849cf80962 0.600000000000 1413890 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": 954620, "vin": [ { "gen": { "height": 954610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019387e3c82ede269a15e99ddba0a95d06cc839ff6de9465df310d849cf80962" } } ], "extra": [ 1, 222, 236, 53, 212, 165, 36, 220, 6, 163, 138, 217, 229, 142, 221, 240, 71, 200, 86, 108, 53, 96, 49, 125, 199, 157, 100, 131, 222, 76, 58, 30, 186, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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