← previous blocknext block →recent activity
Analyzing
Block #107,848,397
13 transactions · 13 stateful · 2026-09-25 08:43:48 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,848,397 · 13 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
1w04w05w16w27w38w49w410w512w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc4646dd5…0b8e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xbe512d56…38f2
0x34b655…2a6f
4 touches
1 conflict
0xb54ff07e…e41d
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
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
6 conflicts on slot 0xecff7c3510…111b43
Audit this contract →
← previous block·next block →recent activity