Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c354617e3c958938952416c84f2a1b433a446314a2814ff96aa3c6decabc79c1

Tx prefix hash: 5c2ecc5bd79759a593dc55ed8ca0c47ff94f4914afa0d32c932f473772b5e147
Tx public key: 8b3a30111dd5835fc76bc1de848fd295ec4d1e2a3a39f7df769767211ab0a97c
Timestamp: 1671356194 Timestamp [UCT]: 2022-12-18 09:36:34 Age [y:d:h:m:s]: 02:031:15:09:20
Block: 655169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544506 RingCT/type: yes/0
Extra: 018b3a30111dd5835fc76bc1de848fd295ec4d1e2a3a39f7df769767211ab0a97c02110000000174b6d784000000000000000000

1 output(s) for total of 4.141456541000 dcy

stealth address amount amount idx
00: ffe3e92dbb5e48c93fb5fec4f9b8cce8be04bf6e6af2a4aea3e8443b7e5f8ff3 4.141456541000 1095716 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": 655179, "vin": [ { "gen": { "height": 655169 } } ], "vout": [ { "amount": 4141456541, "target": { "key": "ffe3e92dbb5e48c93fb5fec4f9b8cce8be04bf6e6af2a4aea3e8443b7e5f8ff3" } } ], "extra": [ 1, 139, 58, 48, 17, 29, 213, 131, 95, 199, 107, 193, 222, 132, 143, 210, 149, 236, 77, 30, 42, 58, 57, 247, 223, 118, 151, 103, 33, 26, 176, 169, 124, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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