← previous blocknext block →recent activity
Analyzing
Block #106,282,967
35 transactions · 29 stateful · 2026-09-19 21:21:13 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.51
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,282,967 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w08w110w211w316w220w025w026w328w430w132w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4ea5b300…4b78
0x34b655…2a6f
6 touches
3 conflicts
0x5d0915af…762d
0x34b655…2a6f
4 touches
1 conflict
0x6cdc7297…56e2
0x34b655…2a6f
4 touches
1 conflict
0x6d59a973…32a9
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x8ce59fa8…e1da
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity