Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96ebefca3afc378aebacb6c73f032b6b3f06b582e63f8ea2154a1c66a2240dcb

Tx prefix hash: e39c4e89e410feaa6dda7ffc2888965ff7a2846ec7e00238e766fe4703ab75ae
Tx public key: 05e98c4eee16398cbc2c61328e007e705a596cf77cf69d78a34685a9696cbc3f
Timestamp: 1577699710 Timestamp [UCT]: 2019-12-30 09:55:10 Age [y:d:h:m:s]: 05:004:00:36:03
Block: 34921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152891 RingCT/type: yes/0
Extra: 0105e98c4eee16398cbc2c61328e007e705a596cf77cf69d78a34685a9696cbc3f0211000000034943cd9f000000000000000000

1 output(s) for total of 470.211325885000 dcy

stealth address amount amount idx
00: c26620b4b77bc0ee0e91dc0c53a7589108178af88d2fa4bcb60b45ff8cc42865 470.211325885000 58832 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": 34931, "vin": [ { "gen": { "height": 34921 } } ], "vout": [ { "amount": 470211325885, "target": { "key": "c26620b4b77bc0ee0e91dc0c53a7589108178af88d2fa4bcb60b45ff8cc42865" } } ], "extra": [ 1, 5, 233, 140, 78, 238, 22, 57, 140, 188, 44, 97, 50, 142, 0, 126, 112, 90, 89, 108, 247, 124, 246, 157, 120, 163, 70, 133, 169, 105, 108, 188, 63, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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