Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8bb452d46e71adf5e4fb9262cc58d4ec63ef26d1968b53b18591c39082a214

Tx prefix hash: 3d5d1e3f262b36553375730aefd2080c3dafcada6068d101145364d902c2a841
Tx public key: 8109d22c92fb3b5d91898d35f6a33e0552d546636d52d14a8edb158662877239
Timestamp: 1734533204 Timestamp [UCT]: 2024-12-18 14:46:44 Age [y:d:h:m:s]: 00:106:11:08:08
Block: 1177958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75839 RingCT/type: yes/0
Extra: 018109d22c92fb3b5d91898d35f6a33e0552d546636d52d14a8edb1586628772390211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aeb7f71219f9ff04222d7e6af2d2c0e72b3b4873a0b6aae86aad4f34581e46a 0.600000000000 1664339 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": 1177968, "vin": [ { "gen": { "height": 1177958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aeb7f71219f9ff04222d7e6af2d2c0e72b3b4873a0b6aae86aad4f34581e46a" } } ], "extra": [ 1, 129, 9, 210, 44, 146, 251, 59, 93, 145, 137, 141, 53, 246, 163, 62, 5, 82, 213, 70, 99, 109, 82, 209, 74, 142, 219, 21, 134, 98, 135, 114, 57, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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