← previous blocknext block →recent activity
Analyzing
Block #107,847,901
20 transactions · 17 stateful · 2026-09-25 08:41:19 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,847,901 · 20 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
1w02w17w28w09w110w211w312w414w517w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
8 touches
6 conflicts
0x221a943e…21d3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0x4155e64d…1d89
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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