← previous blocknext block →recent activity
Analyzing
Block #105,575,608
14 transactions · 14 stateful · 2026-09-17 09:58:33 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,575,608 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w311w412w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24d6bacf…5316
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8feb2121…031a
0x34b655…2a6f
4 touches
1 conflict
0x9d7ac3b9…22f8
0x34b655…2a6f
4 touches
1 conflict
0xb58ed141…c32e
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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
3 conflicts on slot 0x24d6bacfbe…5f5316
Audit this contract →
← previous block·next block →recent activity