← previous blocknext block →recent activity
Analyzing
Block #107,816,650
36 transactions · 31 stateful · 2026-09-25 06:04:01 UTC
Parallelism
61/100
Blocked
65%
Avg conflicts / tx
1.67
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #107,816,650 · 36 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w18w19w213w014w115w217w018w119w220w321w422w523w624w725w826w231w932w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x4fa9b4d7…e7e6
0x34b655…2a6f
8 touches
6 conflicts
0xe714508e…de12
0x34b655…2a6f
6 touches
3 conflicts
0x00f245ce…1e10
0x34b655…2a6f
6 touches
3 conflicts
0xa27126ab…f828
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
28 conflicts on slot 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity