Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f17c9d3fc29292ffb1dac4b88474f5ff9c7db2d8cad04a00f3c983e8b5c12acd

Tx prefix hash: 0f56a1c3b771b86b52e4b8921727d5f55b6bad04b28268f25a2809326893d406
Tx public key: eeef9ee0b7d34766d10f1e8862224489847bd36fb923da83af748a83442a2313
Timestamp: 1725639655 Timestamp [UCT]: 2024-09-06 16:20:55 Age [y:d:h:m:s]: 00:124:11:57:39
Block: 1104312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89038 RingCT/type: yes/0
Extra: 01eeef9ee0b7d34766d10f1e8862224489847bd36fb923da83af748a83442a2313021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bbcb87333ec6da0c7a649d5a5e8bebb7664fc6d9e7282ec845028c503f017be 0.600000000000 1581405 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": 1104322, "vin": [ { "gen": { "height": 1104312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bbcb87333ec6da0c7a649d5a5e8bebb7664fc6d9e7282ec845028c503f017be" } } ], "extra": [ 1, 238, 239, 158, 224, 183, 211, 71, 102, 209, 15, 30, 136, 98, 34, 68, 137, 132, 123, 211, 111, 185, 35, 218, 131, 175, 116, 138, 131, 68, 42, 35, 19, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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