← previous blocknext block →recent activity
Analyzing
Block #107,643,308
23 transactions · 21 stateful · 2026-09-24 15:30:10 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,643,308 · 23 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
1w02w08w09w110w111w013w114w115w216w317w421w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x3ff9db2e…22f6
0x34b655…2a6f
6 touches
3 conflicts
0xeb24430e…f3d1
0x34b655…2a6f
6 touches
3 conflicts
0xab41643c…f9bf
0x34b655…2a6f
6 touches
3 conflicts
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x9aa4f570…13ab
0x34b655…2a6f
4 touches
1 conflict
0xb40b0559…27c3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity