Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88b7289b07a95da5d936d207fc40b3dbab0d9e6bbedc58fb3be687a7ce33ba76

Tx prefix hash: dd568f05a1e5eed916c25898b1e8993494d89f3250ee1250cccdb53f2d35b907
Tx public key: baca1e555a166e74fe48cb67c5e09f4bba9471cc13117d7f0a9892ada452aa1c
Timestamp: 1721503670 Timestamp [UCT]: 2024-07-20 19:27:50 Age [y:d:h:m:s]: 00:126:20:23:35
Block: 1070023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90772 RingCT/type: yes/0
Extra: 01baca1e555a166e74fe48cb67c5e09f4bba9471cc13117d7f0a9892ada452aa1c021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94fb765b5d6cdbb3d26830c81bab524af4ed2b7e751edf1e6b4ce9f01f6cf1a9 0.600000000000 1541686 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": 1070033, "vin": [ { "gen": { "height": 1070023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94fb765b5d6cdbb3d26830c81bab524af4ed2b7e751edf1e6b4ce9f01f6cf1a9" } } ], "extra": [ 1, 186, 202, 30, 85, 90, 22, 110, 116, 254, 72, 203, 103, 197, 224, 159, 75, 186, 148, 113, 204, 19, 17, 125, 127, 10, 152, 146, 173, 164, 82, 170, 28, 2, 17, 0, 0, 0, 7, 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