← previous blocknext block →recent activity
Analyzing
Block #106,188,319
32 transactions · 29 stateful · 2026-09-19 13:24:48 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,188,319 · 32 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
4w05w16w112w216w318w419w520w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7bbf1c1…d16d
0x34b655…2a6f
14 touches
21 conflicts
0xd41f5136…97c6
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x159cff26…7665
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 0xd7bbf1c12d…33d16d
Audit this contract →
← previous block·next block →recent activity