Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41c69196bbecd1e2da6520291882e51911bb23f0c63f4fc33e2aaefaa1f5d5e2

Tx prefix hash: 2238f141a80494166e83993ae34d9e1b61814f0f158eb96e032f81286ac03bb7
Tx public key: a89d7ae8ee73a6b08133cc695b3770c2d5deaeea774c6115cfb0543366e78086
Timestamp: 1576427206 Timestamp [UCT]: 2019-12-15 16:26:46 Age [y:d:h:m:s]: 05:057:05:40:02
Block: 27762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1187314 RingCT/type: yes/0
Extra: 01a89d7ae8ee73a6b08133cc695b3770c2d5deaeea774c6115cfb0543366e78086021100000024ad433a0b000000000000000000

1 output(s) for total of 496.608141290000 dcy

stealth address amount amount idx
00: c0ac55ffd868bd74af7d5465561fce75c7ea5f061616540a58bb681e464d515d 496.608141290000 45812 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": 27772, "vin": [ { "gen": { "height": 27762 } } ], "vout": [ { "amount": 496608141290, "target": { "key": "c0ac55ffd868bd74af7d5465561fce75c7ea5f061616540a58bb681e464d515d" } } ], "extra": [ 1, 168, 157, 122, 232, 238, 115, 166, 176, 129, 51, 204, 105, 91, 55, 112, 194, 213, 222, 174, 234, 119, 76, 97, 21, 207, 176, 84, 51, 102, 231, 128, 134, 2, 17, 0, 0, 0, 36, 173, 67, 58, 11, 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