← previous blocknext block →recent activity
Analyzing
Block #107,794,773
25 transactions · 24 stateful · 2026-09-25 04:13:56 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,794,773 · 25 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
3w04w16w08w011w012w113w214w115w216w317w222w123w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6c8ab591…10e6
0x34b655…2a6f
6 touches
3 conflicts
0x0311862a…7c5c
0x34b655…2a6f
4 touches
1 conflict
0x04d0d005…67c9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3053ffcc…717e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity