← previous blocknext block →recent activity
Analyzing
Block #108,533,317
19 transactions · 18 stateful · 2026-09-27 18:11:00 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,533,317 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
10 touches
10 conflicts
0x1c414c9c…ccc1
0x34b655…2a6f
10 touches
10 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
10 touches
10 conflicts
0x466771e2…9731
0x34b655…2a6f
10 touches
10 conflicts
0x5969523e…5191
0x34b655…2a6f
10 touches
10 conflicts
0x7f8e3158…9dfd
0x34b655…2a6f
10 touches
10 conflicts
0x88fc2a68…3918
0x34b655…2a6f
10 touches
10 conflicts
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity