Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b01c389914ffd8bbed2de2553cc4a2f11ef0eef580e11c6fce7ce7cfe06c0ce4

Tx prefix hash: 5670b39414d4118dcbc5617f66518d6faabbf8002e96c68a047c1c87ce1c73aa
Tx public key: 7433d6bcebea0c178f53f858e1e9452e1c6aadb6f42b15f1fae8985cf2a14387
Timestamp: 1640867091 Timestamp [UCT]: 2021-12-30 12:24:51 Age [y:d:h:m:s]: 03:040:13:45:03
Block: 406744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 807736 RingCT/type: yes/0
Extra: 017433d6bcebea0c178f53f858e1e9452e1c6aadb6f42b15f1fae8985cf2a14387021100000001ed5d3ead000000000000000000

1 output(s) for total of 27.561077084000 dcy

stealth address amount amount idx
00: 4c7955f4cd9df172edb10a4a34ae6cf1da4f0f0e539f016eaa233c93b50ea8a3 27.561077084000 807816 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": 406754, "vin": [ { "gen": { "height": 406744 } } ], "vout": [ { "amount": 27561077084, "target": { "key": "4c7955f4cd9df172edb10a4a34ae6cf1da4f0f0e539f016eaa233c93b50ea8a3" } } ], "extra": [ 1, 116, 51, 214, 188, 235, 234, 12, 23, 143, 83, 248, 88, 225, 233, 69, 46, 28, 106, 173, 182, 244, 43, 21, 241, 250, 232, 152, 92, 242, 161, 67, 135, 2, 17, 0, 0, 0, 1, 237, 93, 62, 173, 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