← previous blocknext block →recent activity
Analyzing
Block #107,813,456
30 transactions · 26 stateful · 2026-09-25 05:47:57 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,813,456 · 30 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
5w08w110w013w014w115w116w217w318w419w520w125w026w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0x2b76a1fb…fdfc
0x34b655…2a6f
6 touches
3 conflicts
0x973b84cc…0613
0x34b655…2a6f
6 touches
3 conflicts
0x4073f47e…39e6
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x6ce7d88f…31ea
0x34b655…2a6f
4 touches
1 conflict
0x3a663e9a…a9ce
0x508254…98bd
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
10 conflicts on slot 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity