Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89aa2e958af45c81706d0cb76121a88eaca0d7b30a9f41263175600ff890ab5b

Tx prefix hash: db681d72cbaa52e0b12586242be2814fa54addf46b06a82f8fcacab9455e943b
Tx public key: cea8f2b6ef3a58c29d52a00ab409f9624658ce62fd90a37a126c0cfd14d3d95a
Timestamp: 1705404427 Timestamp [UCT]: 2024-01-16 11:27:07 Age [y:d:h:m:s]: 01:077:05:00:04
Block: 936535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316275 RingCT/type: yes/0
Extra: 01cea8f2b6ef3a58c29d52a00ab409f9624658ce62fd90a37a126c0cfd14d3d95a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a50cf78a7df07462bd289963391fde80723bbc51835f5e56efb3803c853e0e 0.600000000000 1394563 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": 936545, "vin": [ { "gen": { "height": 936535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a50cf78a7df07462bd289963391fde80723bbc51835f5e56efb3803c853e0e" } } ], "extra": [ 1, 206, 168, 242, 182, 239, 58, 88, 194, 157, 82, 160, 10, 180, 9, 249, 98, 70, 88, 206, 98, 253, 144, 163, 122, 18, 108, 12, 253, 20, 211, 217, 90, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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