← previous blocknext block →recent activity
Analyzing
Block #107,813,688
18 transactions · 16 stateful · 2026-09-25 05:49:07 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,813,688 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w110w011w112w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x429c8b35…0f5c
0x34b655…2a6f
4 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
4 touches
1 conflict
0x9901e91f…179b
0x34b655…2a6f
4 touches
1 conflict
0xba522812…1f1f
0x34b655…2a6f
4 touches
1 conflict
0xc64d3656…0c1c
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
3 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity