← previous blocknext block →recent activity
Analyzing
Block #107,823,692
27 transactions · 25 stateful · 2026-09-25 06:39:28 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,823,692 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w015w116w117w018w119w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x25144f94…1854
0x34b655…2a6f
6 touches
3 conflicts
0xf895a72a…7aa3
0x34b655…2a6f
6 touches
3 conflicts
0x39e6e629…9f6c
0x34b655…2a6f
6 touches
3 conflicts
0xe61442e1…1337
0x34b655…2a6f
6 touches
3 conflicts
0x301e1c77…9e30
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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