← previous blocknext block →recent activity
Analyzing
Block #107,451,201
16 transactions · 16 stateful · 2026-09-23 23:22:33 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,451,201 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w08w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf51a94f0…f9b9
0x34b655…2a6f
4 touches
1 conflict
0x01352f43…c797
0x34b655…2a6f
4 touches
1 conflict
0x7cf715cd…0e55
0x34b655…2a6f
4 touches
1 conflict
0x847f739c…1e06
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x190b178a…c154
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf51a94f02f…87f9b9
Audit this contract →
← previous block·next block →recent activity