Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: facaff8fbfaaf1403b8ffb5177bd68aae45240a93d154bedcfc2dbcfe49eb31b

Tx prefix hash: 9ff36b662edc8de7bef65f90096b2b85c40a62ad0565ceedcdf0af2a22564327
Tx public key: cb1d2b4d14fe7f4c0773d12a7269178ed3a1b88064723dfb533b977f11be7f8a
Timestamp: 1704217500 Timestamp [UCT]: 2024-01-02 17:45:00 Age [y:d:h:m:s]: 01:165:11:51:22
Block: 926699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379331 RingCT/type: yes/0
Extra: 01cb1d2b4d14fe7f4c0773d12a7269178ed3a1b88064723dfb533b977f11be7f8a0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af5315a0115fb1b7577399539ffce27fcf970d7e64b1ac5623a838c290d976a2 0.600000000000 1384495 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": 926709, "vin": [ { "gen": { "height": 926699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af5315a0115fb1b7577399539ffce27fcf970d7e64b1ac5623a838c290d976a2" } } ], "extra": [ 1, 203, 29, 43, 77, 20, 254, 127, 76, 7, 115, 209, 42, 114, 105, 23, 142, 211, 161, 184, 128, 100, 114, 61, 251, 83, 59, 151, 127, 17, 190, 127, 138, 2, 17, 0, 0, 0, 9, 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