← previous blocknext block →recent activity
Analyzing
Block #108,549,623
28 transactions · 25 stateful · 2026-09-27 19:33:06 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,549,623 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w111w014w015w116w117w218w319w222w123w124w025w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8195e8a9…1407
0x34b655…2a6f
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x2bb802b7…e475
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x8195e8a933…fd1407
Audit this contract →
← previous block·next block →recent activity