← previous blocknext block →recent activity
Analyzing
Block #106,281,637
27 transactions · 26 stateful · 2026-09-19 21:14:31 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,281,637 · 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
2w03w04w15w06w07w18w112w013w214w316w117w418w519w620w721w022w123w226w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b92a098…5b98
0x34b655…2a6f
12 touches
15 conflicts
0xdc90bed5…58a9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x86cea35b…bdff
0x34b655…2a6f
6 touches
3 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
4 touches
1 conflict
0xa4279852…769b
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
15 conflicts on slot 0x1b92a0985f…0b5b98
Audit this contract →
← previous block·next block →recent activity