Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 950f07ba6bc1d29934f0cbb604da180bf5a3b8346f54d3c4bd9b871301e75418

Tx prefix hash: c46a0f61dfcfca408e8d5e006dd844a13e76071916af525405b60eaaa8c67516
Tx public key: 35ab3d6869c10c1d5666128b6fceead3ab2114ed13a29817b7c4308b5719193d
Timestamp: 1636073213 Timestamp [UCT]: 2021-11-05 00:46:53 Age [y:d:h:m:s]: 03:361:10:32:08
Block: 367538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1034357 RingCT/type: yes/0
Extra: 0135ab3d6869c10c1d5666128b6fceead3ab2114ed13a29817b7c4308b5719193d0211000000176e80e2c6000000000000000000

1 output(s) for total of 37.171420093000 dcy

stealth address amount amount idx
00: 51fa229133191c609f6b1d7bdfb7c934e1f40f80aaf8b1399f9d8b98ea559323 37.171420093000 745744 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": 367548, "vin": [ { "gen": { "height": 367538 } } ], "vout": [ { "amount": 37171420093, "target": { "key": "51fa229133191c609f6b1d7bdfb7c934e1f40f80aaf8b1399f9d8b98ea559323" } } ], "extra": [ 1, 53, 171, 61, 104, 105, 193, 12, 29, 86, 102, 18, 139, 111, 206, 234, 211, 171, 33, 20, 237, 19, 162, 152, 23, 183, 196, 48, 139, 87, 25, 25, 61, 2, 17, 0, 0, 0, 23, 110, 128, 226, 198, 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