Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faf66f7c0defd67f50284a4deb07edbfe6b3fa967e826980658203d0861f6a6b

Tx prefix hash: b9adc41890d313f25be99fcd9aff84436c3049b651f9af499b6cf699a8aa2c4d
Tx public key: afd65fe7ab8bc3f110a5e7cd0effb3bfa7b29215da1576cac68882bdfefc5504
Timestamp: 1708979958 Timestamp [UCT]: 2024-02-26 20:39:18 Age [y:d:h:m:s]: 01:000:11:03:38
Block: 966205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261303 RingCT/type: yes/0
Extra: 01afd65fe7ab8bc3f110a5e7cd0effb3bfa7b29215da1576cac68882bdfefc55040211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 686b05e0aaccb20709924856a1a3139521d68f3df9305062a410d222df140671 0.600000000000 1425962 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": 966215, "vin": [ { "gen": { "height": 966205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "686b05e0aaccb20709924856a1a3139521d68f3df9305062a410d222df140671" } } ], "extra": [ 1, 175, 214, 95, 231, 171, 139, 195, 241, 16, 165, 231, 205, 14, 255, 179, 191, 167, 178, 146, 21, 218, 21, 118, 202, 198, 136, 130, 189, 254, 252, 85, 4, 2, 17, 0, 0, 0, 1, 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