← previous blocknext block →recent activity
Analyzing
Block #107,795,293
21 transactions · 20 stateful · 2026-09-25 04:16:33 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,795,293 · 21 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
4w05w16w212w013w114w215w316w418w319w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xaaf69712…5347
0x34b655…2a6f
6 touches
3 conflicts
0xaeaefe5d…f91b
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xe763a93c…e90b
0x34b655…2a6f
6 touches
3 conflicts
0x03a47c2a…8884
0x40c49f…2af0
5 touches
3 conflicts
0xe0d06fc3…d081
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 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity