Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d299d7254a16247a11b60cc3023f7307c4856b81124fefa5381da3cfa2e8f10e

Tx prefix hash: d5c1fc3af3c4bc2ff0bac29524c7f6645d11371aef3c0df1fa33837a7143459d
Tx public key: a9b3b8d4f3233798181d2e15bf495b17308279eb5ce5003361866c87e58f3c9e
Timestamp: 1685851749 Timestamp [UCT]: 2023-06-04 04:09:09 Age [y:d:h:m:s]: 01:222:14:46:05
Block: 774695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420519 RingCT/type: yes/0
Extra: 01a9b3b8d4f3233798181d2e15bf495b17308279eb5ce5003361866c87e58f3c9e02110000000333af99f4000000000000000000

1 output(s) for total of 1.663849501000 dcy

stealth address amount amount idx
00: 814e02345a02f29436ebde2c8b9018b3d2e78d09610c9344e6a5dda3cfd0c3f3 1.663849501000 1224180 of 0

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": 774705, "vin": [ { "gen": { "height": 774695 } } ], "vout": [ { "amount": 1663849501, "target": { "key": "814e02345a02f29436ebde2c8b9018b3d2e78d09610c9344e6a5dda3cfd0c3f3" } } ], "extra": [ 1, 169, 179, 184, 212, 243, 35, 55, 152, 24, 29, 46, 21, 191, 73, 91, 23, 48, 130, 121, 235, 92, 229, 0, 51, 97, 134, 108, 135, 229, 143, 60, 158, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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