← previous blocknext block →recent activity
Analyzing
Block #107,848,500
21 transactions · 16 stateful · 2026-09-25 08:44:19 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,848,500 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w18w29w310w411w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbac338fb…5aec
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x0e942dae…8cd9
0x34b655…2a6f
8 touches
6 conflicts
0xcb21158b…f18d
0x34b655…2a6f
8 touches
6 conflicts
0xecff7c35…1b43
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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
10 conflicts on slot 0xbac338fbec…e55aec
Audit this contract →
← previous block·next block →recent activity