← previous blocknext block →recent activity
Analyzing
Block #105,851,572
27 transactions · 26 stateful · 2026-09-18 09:08:58 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,851,572 · 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
1w04w05w16w08w19w010w213w114w215w316w417w518w619w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81716ce9…095f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x0e7838ac…6a89
0x34b655…2a6f
10 touches
10 conflicts
0x4abfb389…18f4
0x34b655…2a6f
6 touches
3 conflicts
0xcc5daa0a…b949
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x206f4379…e08a
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x81716ce924…61095f
Audit this contract →
← previous block·next block →recent activity