← previous blocknext block →recent activity
Analyzing
Block #107,823,310
19 transactions · 19 stateful · 2026-09-25 06:37:32 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,823,310 · 19 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
1w02w16w27w08w29w110w211w312w413w518w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6913fc36…ae5d
0x34b655…2a6f
12 touches
15 conflicts
0xdcd07321…1c31
0x34b655…2a6f
10 touches
10 conflicts
0xc3baa205…f26e
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xad5ae3cc…79ea
0xd32edf…ff58
7 touches
6 conflicts
0x429c8b35…0f5c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x6913fc36d7…0bae5d
Audit this contract →
← previous block·next block →recent activity