← previous blocknext block →recent activity
Analyzing
Block #105,881,614
32 transactions · 28 stateful · 2026-09-18 11:40:10 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,881,614 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w114w016w217w118w219w320w321w422w529w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x297de2d5…7396
0x34b655…2a6f
10 touches
10 conflicts
0x64b18423…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0x64f182c6…e42d
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity