Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a63bebf93d71bc6c410b952c242adfedf08164f2505157d9b8a56594d6eabafb

Tx prefix hash: ed3778c9c5d36b6ffa786724a1666325398ff96179bef2cda00abdc638c16673
Tx public key: df33f21bb700e16a7dd403d376d5a20706142925b220a357f48a7263bd918c9d
Timestamp: 1700947855 Timestamp [UCT]: 2023-11-25 21:30:55 Age [y:d:h:m:s]: 01:361:23:49:23
Block: 899601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517616 RingCT/type: yes/0
Extra: 01df33f21bb700e16a7dd403d376d5a20706142925b220a357f48a7263bd918c9d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.641576472000 dcy

stealth address amount amount idx
00: f317700c5ba0df6c6e2d63294a817c14dd3aa792009639fefe73b3f62bae7bb5 0.641576472000 1356060 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": 899611, "vin": [ { "gen": { "height": 899601 } } ], "vout": [ { "amount": 641576472, "target": { "key": "f317700c5ba0df6c6e2d63294a817c14dd3aa792009639fefe73b3f62bae7bb5" } } ], "extra": [ 1, 223, 51, 242, 27, 183, 0, 225, 106, 125, 212, 3, 211, 118, 213, 162, 7, 6, 20, 41, 37, 178, 32, 163, 87, 244, 138, 114, 99, 189, 145, 140, 157, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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