← previous blocknext block →recent activity
Analyzing
Block #106,193,289
11 transactions · 11 stateful · 2026-09-19 13:49:48 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,193,289 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7826b5b…166a
0x34b655…2a6f
4 touches
1 conflict
0x6d426cdf…360d
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x82fd45e4…0935
0x34b655…2a6f
4 touches
1 conflict
0xca007720…fe66
0x34b655…2a6f
4 touches
1 conflict
0xd2a47eb3…759c
0x34b655…2a6f
4 touches
1 conflict
0xd41f5136…97c6
0x34b655…2a6f
4 touches
1 conflict
0xd62f3741…b903
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
1 conflict on slot 0xe7826b5bba…04166a
Audit this contract →
← previous block·next block →recent activity