Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2358d3b64dbd3ada0c7a2bec3dafa318cffd9a2430ab787b99bc5a8a0260113e

Tx prefix hash: ff916da92e5eb1210ea5122033bd1c8b9a855ef34de62549e6e018bb10a22cfc
Tx public key: 7bbd21ba0d487f4ae033adf981dd342983f425f46962df4abced6dc163c93b7d
Timestamp: 1721481018 Timestamp [UCT]: 2024-07-20 13:10:18 Age [y:d:h:m:s]: 00:298:20:40:41
Block: 1069828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213548 RingCT/type: yes/0
Extra: 017bbd21ba0d487f4ae033adf981dd342983f425f46962df4abced6dc163c93b7d021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d2d9a59fc509ace9f1b7ea93aa96127c59d99255e74bb45fca705b087b10e2 0.600000000000 1541413 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": 1069838, "vin": [ { "gen": { "height": 1069828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d2d9a59fc509ace9f1b7ea93aa96127c59d99255e74bb45fca705b087b10e2" } } ], "extra": [ 1, 123, 189, 33, 186, 13, 72, 127, 74, 224, 51, 173, 249, 129, 221, 52, 41, 131, 244, 37, 244, 105, 98, 223, 74, 188, 237, 109, 193, 99, 201, 59, 125, 2, 17, 0, 0, 0, 6, 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