Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee2d7fecf2e7a1784e931c6d5ef84b8af3e3e713ee33e69b051fc871129ade82

Tx prefix hash: a60e5f3b12caaa53e48271d5680ff2dc91d591b9a15725a58dda4d0c4d4b9d72
Tx public key: ab4ed31a96a6bd741e8fc157cde52f4f5cee484fa810ea814668ad4c6ca396da
Timestamp: 1727122471 Timestamp [UCT]: 2024-09-23 20:14:31 Age [y:d:h:m:s]: 00:200:03:53:14
Block: 1116604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142880 RingCT/type: yes/0
Extra: 01ab4ed31a96a6bd741e8fc157cde52f4f5cee484fa810ea814668ad4c6ca396da021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d77ff171f7d4089a15e1ec82086226eb4a9c45d73b5a2a258fe9a3d50dc986f3 0.600000000000 1597147 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": 1116614, "vin": [ { "gen": { "height": 1116604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d77ff171f7d4089a15e1ec82086226eb4a9c45d73b5a2a258fe9a3d50dc986f3" } } ], "extra": [ 1, 171, 78, 211, 26, 150, 166, 189, 116, 30, 143, 193, 87, 205, 229, 47, 79, 92, 238, 72, 79, 168, 16, 234, 129, 70, 104, 173, 76, 108, 163, 150, 218, 2, 17, 0, 0, 0, 8, 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