Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6661139017cb4469b8aa766e15895f24858c6c7b4ab6e145f2251b8341f70ba1

Tx prefix hash: aaa05179125d96fb771062935592e7e7533b5b68c750acdbdee5fb0f411530d1
Tx public key: ffeb01e5c6906f73d5fa348fac73a86fc4b3f8b8d1932adcb4fa7dcca4d2b286
Timestamp: 1705628295 Timestamp [UCT]: 2024-01-19 01:38:15 Age [y:d:h:m:s]: 01:305:22:43:12
Block: 938387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477491 RingCT/type: yes/0
Extra: 01ffeb01e5c6906f73d5fa348fac73a86fc4b3f8b8d1932adcb4fa7dcca4d2b2860211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1adb2df45c9137c51fcaa8b5e6e3b89de749c7afd6ee4b2f1e3bb9287a87f85 0.600000000000 1396457 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": 938397, "vin": [ { "gen": { "height": 938387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1adb2df45c9137c51fcaa8b5e6e3b89de749c7afd6ee4b2f1e3bb9287a87f85" } } ], "extra": [ 1, 255, 235, 1, 229, 198, 144, 111, 115, 213, 250, 52, 143, 172, 115, 168, 111, 196, 179, 248, 184, 209, 147, 42, 220, 180, 250, 125, 204, 164, 210, 178, 134, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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