← previous blocknext block →recent activity
Analyzing
Block #107,823,539
18 transactions · 18 stateful · 2026-09-25 06:38:42 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,539 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w07w08w19w210w311w412w515w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xa2c4d203…05b6
0x34b655…2a6f
6 touches
3 conflicts
0xa7ba83b5…d0a8
0x34b655…2a6f
6 touches
3 conflicts
0xa8753ff9…2a9f
0x34b655…2a6f
6 touches
3 conflicts
0xb5605df4…7686
0x34b655…2a6f
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
6 touches
3 conflicts
0x232b0b19…d946
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity