← previous blocknext block →recent activity
Analyzing
Block #105,925,571
23 transactions · 22 stateful · 2026-09-18 15:22:18 UTC
Parallelism
83/100
Blocked
41%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,925,571 · 23 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
1w02w13w04w15w06w110w111w012w113w214w316w018w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0405beaf…373c
0x6f6493…b480
8 touches
6 conflicts
0x9234f6f4…a59b
0x6f6493…b480
8 touches
6 conflicts
0xcc3c58ef…3870
0x6f6493…b480
8 touches
6 conflicts
0xd238b4ed…1790
0x6f6493…b480
8 touches
6 conflicts
0xdbc38435…ccda
0x6f6493…b480
8 touches
6 conflicts
0xdbc38435…ccde
0x6f6493…b480
8 touches
6 conflicts
0xf3af78bb…a4b1
0x6f6493…b480
8 touches
6 conflicts
0xfbfe3f92…ef03
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 0x0405beafc6…2a373c
Audit this contract →
← previous block·next block →recent activity