Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3aeaeaeda9fabd02b78b195e700e0612020b924cbe19031e7a993e1816c7cbf8

Tx prefix hash: f6ed9ac0505719524200411f954bfc58eba44e0b33dcc97d8c5129474e87196f
Tx public key: 11f0e51e3f27666d56625cac9f81e4330725d46b6f5af436dc09a3f972af37ae
Timestamp: 1636506811 Timestamp [UCT]: 2021-11-10 01:13:31 Age [y:d:h:m:s]: 03:169:10:23:14
Block: 371055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899504 RingCT/type: yes/0
Extra: 0111f0e51e3f27666d56625cac9f81e4330725d46b6f5af436dc09a3f972af37ae0211000000024f792ffd000000000000000000

1 output(s) for total of 36.186677213000 dcy

stealth address amount amount idx
00: 9f400b0e404c7625d3598734071823e62d2bf6224c60b30e899c0ffb36536d5f 36.186677213000 752017 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": 371065, "vin": [ { "gen": { "height": 371055 } } ], "vout": [ { "amount": 36186677213, "target": { "key": "9f400b0e404c7625d3598734071823e62d2bf6224c60b30e899c0ffb36536d5f" } } ], "extra": [ 1, 17, 240, 229, 30, 63, 39, 102, 109, 86, 98, 92, 172, 159, 129, 228, 51, 7, 37, 212, 107, 111, 90, 244, 54, 220, 9, 163, 249, 114, 175, 55, 174, 2, 17, 0, 0, 0, 2, 79, 121, 47, 253, 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