← previous blocknext block →recent activity
Analyzing
Block #107,816,594
16 transactions · 15 stateful · 2026-09-25 06:03:44 UTC
Parallelism
56/100
Blocked
53%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,816,594 · 16 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
1w02w16w07w18w29w310w411w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0x44b4869a…fe59
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xb3c08d5e…42cd
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00e21a9f…3583
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
10 conflicts on slot 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity