Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e70f9d1b3c1f2fdd93ff8e63ae93dce6573e78a03dccbc47be544685118d95d

Tx prefix hash: 54cfef06215409c062b37c68dfae80956ff82626851fb3dd04c7bee60c2c6a84
Tx public key: c8c41e42363ae1dacd8e07fabdad988539f8e51b041cd011d4fa853bb9a8c028
Timestamp: 1705747245 Timestamp [UCT]: 2024-01-20 10:40:45 Age [y:d:h:m:s]: 01:085:03:04:19
Block: 939361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321953 RingCT/type: yes/0
Extra: 01c8c41e42363ae1dacd8e07fabdad988539f8e51b041cd011d4fa853bb9a8c02802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 776a5e2cb97e12522f806662366c942650bcf61fd18feaa938f72f81bea23391 0.600000000000 1397461 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": 939371, "vin": [ { "gen": { "height": 939361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "776a5e2cb97e12522f806662366c942650bcf61fd18feaa938f72f81bea23391" } } ], "extra": [ 1, 200, 196, 30, 66, 54, 58, 225, 218, 205, 142, 7, 250, 189, 173, 152, 133, 57, 248, 229, 27, 4, 28, 208, 17, 212, 250, 133, 59, 185, 168, 192, 40, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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