← previous blocknext block →recent activity
Analyzing
Block #106,809,641
27 transactions · 23 stateful · 2026-09-21 17:32:55 UTC
Parallelism
70/100
Blocked
35%
Avg conflicts / tx
0.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,809,641 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w19w012w219w320w421w522w623w726w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01f19c33…170d
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x56f201a4…7346
0x34b655…2a6f
8 touches
6 conflicts
0xb961b84e…e6e1
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
6 touches
3 conflicts
0xad862891…5d02
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x01f19c3396…f1170d
Audit this contract →
← previous block·next block →recent activity