Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23da405180c7b4c7e1b647cf720a9a5753c4ed0356d94286fdef9586b9cbc63b

Tx prefix hash: 357261c7f1c9ee98b6a342bd761903fd774222817ee877dca916b160fefe6ef4
Tx public key: b04182a0da4be5cf97c9f9b72a2879a63f31ecce0ac411a458152f33f32aca10
Timestamp: 1721655724 Timestamp [UCT]: 2024-07-22 13:42:04 Age [y:d:h:m:s]: 00:237:21:40:15
Block: 1071269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169974 RingCT/type: yes/0
Extra: 01b04182a0da4be5cf97c9f9b72a2879a63f31ecce0ac411a458152f33f32aca10021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6c3651c06c32c49aa922f8d00100af88099243a30e8ffc7877b4ab462541cf8 0.600000000000 1543430 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": 1071279, "vin": [ { "gen": { "height": 1071269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6c3651c06c32c49aa922f8d00100af88099243a30e8ffc7877b4ab462541cf8" } } ], "extra": [ 1, 176, 65, 130, 160, 218, 75, 229, 207, 151, 201, 249, 183, 42, 40, 121, 166, 63, 49, 236, 206, 10, 196, 17, 164, 88, 21, 47, 51, 243, 42, 202, 16, 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