Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38c2a9d4a6982268d033bb97f38ebfaa3db0ccb831bc8efbc3b181638e3913e4

Tx prefix hash: f6c7b52596332aefd6d69328d57d7824cc26eb08a655b55534d5c843960b6f4b
Tx public key: bb8c9c4b60101709a4e21afff473d937cae079cbd15dc301691f5d2ec0ec1458
Timestamp: 1733556943 Timestamp [UCT]: 2024-12-07 07:35:43 Age [y:d:h:m:s]: 00:120:02:55:12
Block: 1169849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85649 RingCT/type: yes/0
Extra: 01bb8c9c4b60101709a4e21afff473d937cae079cbd15dc301691f5d2ec0ec14580211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26af20ef6de32149dd46940d9f23c25ecc2fc01107adb01b3ca63b6a633898c4 0.600000000000 1655574 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": 1169859, "vin": [ { "gen": { "height": 1169849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26af20ef6de32149dd46940d9f23c25ecc2fc01107adb01b3ca63b6a633898c4" } } ], "extra": [ 1, 187, 140, 156, 75, 96, 16, 23, 9, 164, 226, 26, 255, 244, 115, 217, 55, 202, 224, 121, 203, 209, 93, 195, 1, 105, 31, 93, 46, 192, 236, 20, 88, 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