← previous blocknext block →recent activity
Analyzing
Block #106,235,656
23 transactions · 23 stateful · 2026-09-19 17:23:08 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.39
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,235,656 · 23 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
1w02w14w25w16w27w39w414w516w622w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9470055…bbf8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xe7aa7f4d…bf1c
0x34b655…2a6f
8 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xfa046684…d50a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
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
21 conflicts on slot 0xf94700553e…5dbbf8
Audit this contract →
← previous block·next block →recent activity