← previous blocknext block →recent activity
Analyzing
Block #106,198,791
20 transactions · 19 stateful · 2026-09-19 14:17:30 UTC
Parallelism
80/100
Blocked
32%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,198,791 · 20 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
1w02w14w05w16w27w314w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe43b345e…a4e3
0x34b655…2a6f
8 touches
6 conflicts
0x2b2e5749…b986
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0x315e07b8…9823
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x0a85a226…83c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xe43b345e79…6aa4e3
Audit this contract →
← previous block·next block →recent activity