Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b3d31712e28de45444f610306aa20ee219b7beff46c9218c6ca3f9558d710a3

Tx prefix hash: 6e555a9f91ec68afcf5c82885b9461499492d0e97c70ad8781aa488a725ca72b
Tx public key: 4f56600531d41d667b25706fad4b219f883922f49e49904db18dc39d9f4a96f7
Timestamp: 1702965510 Timestamp [UCT]: 2023-12-19 05:58:30 Age [y:d:h:m:s]: 01:148:00:39:27
Block: 916337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366950 RingCT/type: yes/0
Extra: 014f56600531d41d667b25706fad4b219f883922f49e49904db18dc39d9f4a96f702110000000875e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e016bdf6517c204156a38ecb6819ae6b730b761724829869a0d3009233f430d 0.600000000000 1373837 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": 916347, "vin": [ { "gen": { "height": 916337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e016bdf6517c204156a38ecb6819ae6b730b761724829869a0d3009233f430d" } } ], "extra": [ 1, 79, 86, 96, 5, 49, 212, 29, 102, 123, 37, 112, 111, 173, 75, 33, 159, 136, 57, 34, 244, 158, 73, 144, 77, 177, 141, 195, 157, 159, 74, 150, 247, 2, 17, 0, 0, 0, 8, 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