← previous blocknext block →recent activity
Analyzing
Block #107,841,654
30 transactions · 25 stateful · 2026-09-25 08:09:52 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,841,654 · 30 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
1w06w17w28w39w310w113w014w115w416w217w518w619w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x508174fb…94d2
0x34b655…2a6f
8 touches
6 conflicts
0xbf9df290…b04d
0x34b655…2a6f
8 touches
6 conflicts
0xa0a8c7a5…3422
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0x138b5855…75c2
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
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 0x508174fbc3…8094d2
Audit this contract →
← previous block·next block →recent activity