Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a68e89497953c6763986cb1bfe4d4a24d71ca64bdc7c0f19aeac55d44422a73

Tx prefix hash: c45242529a572133ae531011074753b7b4c453aa5d882f01ce24f3d7e46e12d5
Tx public key: 0c989868eb33f0b7634193304d47abf8ec4babc6d6fddcbea2754bc6b6cce41d
Timestamp: 1720222064 Timestamp [UCT]: 2024-07-05 23:27:44 Age [y:d:h:m:s]: 00:252:01:27:55
Block: 1059393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180102 RingCT/type: yes/0
Extra: 010c989868eb33f0b7634193304d47abf8ec4babc6d6fddcbea2754bc6b6cce41d0211000000048fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3e0960dbf9dfc81c13ea837e8ae2d4fc5aa57345085b98157676905992858b5 0.600000000000 1529860 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": 1059403, "vin": [ { "gen": { "height": 1059393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3e0960dbf9dfc81c13ea837e8ae2d4fc5aa57345085b98157676905992858b5" } } ], "extra": [ 1, 12, 152, 152, 104, 235, 51, 240, 183, 99, 65, 147, 48, 77, 71, 171, 248, 236, 75, 171, 198, 214, 253, 220, 190, 162, 117, 75, 198, 182, 204, 228, 29, 2, 17, 0, 0, 0, 4, 143, 218, 155, 45, 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