← previous blocknext block →recent activity
Analyzing
Block #106,099,613
11 transactions · 11 stateful · 2026-09-19 05:58:22 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,099,613 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x035cce55…b55f
0x6f6493…b480
8 touches
6 conflicts
0x04de7739…20bb
0x6f6493…b480
8 touches
6 conflicts
0x1e53b08c…c29e
0x6f6493…b480
8 touches
6 conflicts
0x2e5eabec…b76f
0x6f6493…b480
8 touches
6 conflicts
0x39de8cab…93e5
0x6f6493…b480
8 touches
6 conflicts
0x3cdb8a42…2231
0x6f6493…b480
8 touches
6 conflicts
0x489ac95d…da67
0x6f6493…b480
8 touches
6 conflicts
0x5bbd8fec…d659
0x6f6493…b480
8 touches
6 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: 0x6f6493e3…08b480
6 conflicts on slot 0x035cce55c4…beb55f
Audit this contract →
← previous block·next block →recent activity