Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99319706780a3be099918c79cccb12d3525e4c018586f8a054c2229bd43d15dc

Tx prefix hash: a9920b543e0908eded33d52b5e0039ebcce81dad81c7e85ae1147041ce74d21d
Tx public key: fbb2d78e41a2198fc721c06e54aa9843e50b982d75c73eeba20ecdd7e2df3a60
Timestamp: 1724394213 Timestamp [UCT]: 2024-08-23 06:23:33 Age [y:d:h:m:s]: 00:228:00:12:32
Block: 1094003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162793 RingCT/type: yes/0
Extra: 01fbb2d78e41a2198fc721c06e54aa9843e50b982d75c73eeba20ecdd7e2df3a60021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e5ea3d0227d33651dbd1e1dcbd106eddbbfc9b648fe318c8a1fc5166defdf91 0.600000000000 1569058 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": 1094013, "vin": [ { "gen": { "height": 1094003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e5ea3d0227d33651dbd1e1dcbd106eddbbfc9b648fe318c8a1fc5166defdf91" } } ], "extra": [ 1, 251, 178, 215, 142, 65, 162, 25, 143, 199, 33, 192, 110, 84, 170, 152, 67, 229, 11, 152, 45, 117, 199, 62, 235, 162, 14, 205, 215, 226, 223, 58, 96, 2, 17, 0, 0, 0, 1, 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