Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f29f3afad61ee1116524060019f2ddcf57c781a4ee14a8e9d5a41819c4a6b36c

Tx prefix hash: c667596a8995eb7ec732f835f8e2b4f18cb42af5ff87115ceb5ea2d7369bfa4e
Tx public key: 3a3b264ffb2f825bdcaca0845d849e076f1b7eb017a4b48107adef232d7b1ba6
Timestamp: 1635315646 Timestamp [UCT]: 2021-10-27 06:20:46 Age [y:d:h:m:s]: 03:011:01:00:59
Block: 361375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 786273 RingCT/type: yes/0
Extra: 013a3b264ffb2f825bdcaca0845d849e076f1b7eb017a4b48107adef232d7b1ba602110000001b1154028c000000000000000000

1 output(s) for total of 38.959647430000 dcy

stealth address amount amount idx
00: a0aa62fd77b9abc40daca078eb5dc33c3de36fd6a327b1dda8c41176e22dfa6f 38.959647430000 735233 of 0

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": 361385, "vin": [ { "gen": { "height": 361375 } } ], "vout": [ { "amount": 38959647430, "target": { "key": "a0aa62fd77b9abc40daca078eb5dc33c3de36fd6a327b1dda8c41176e22dfa6f" } } ], "extra": [ 1, 58, 59, 38, 79, 251, 47, 130, 91, 220, 172, 160, 132, 93, 132, 158, 7, 111, 27, 126, 176, 23, 164, 180, 129, 7, 173, 239, 35, 45, 123, 27, 166, 2, 17, 0, 0, 0, 27, 17, 84, 2, 140, 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