Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb9319c23d034d879d752b8a3b5a9f2b2c1af0bcedad1ba6699e647239f91244

Tx prefix hash: 7992049959e4645d0bae67efaff445baa2b1ff52a0dce75e3dabc7807f09997b
Tx public key: 2747b57e271227eb04ee310085c8a43821b747bd7ef832f6087b2452e0c96d68
Timestamp: 1697662235 Timestamp [UCT]: 2023-10-18 20:50:35 Age [y:d:h:m:s]: 01:235:10:37:51
Block: 872562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429346 RingCT/type: yes/0
Extra: 012747b57e271227eb04ee310085c8a43821b747bd7ef832f6087b2452e0c96d6802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.788569363000 dcy

stealth address amount amount idx
00: b1ddae84e857b9138442749081ca79655196ec218ad1b7fa0b7f8e4db9d700e1 0.788569363000 1327652 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": 872572, "vin": [ { "gen": { "height": 872562 } } ], "vout": [ { "amount": 788569363, "target": { "key": "b1ddae84e857b9138442749081ca79655196ec218ad1b7fa0b7f8e4db9d700e1" } } ], "extra": [ 1, 39, 71, 181, 126, 39, 18, 39, 235, 4, 238, 49, 0, 133, 200, 164, 56, 33, 183, 71, 189, 126, 248, 50, 246, 8, 123, 36, 82, 224, 201, 109, 104, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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