← previous blocknext block →recent activity
Analyzing
Block #111,847,931
23 transactions · 23 stateful · 2026-10-09 08:25:28 UTC
Parallelism
87/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #111,847,931 · 23 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
1w02w03w14w05w16w17w08w116w217w118w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c560816…447c
0x34b655…2a6f
6 touches
3 conflicts
0xf5eb49bf…816a
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0058
0x1b6862…e19c
4 touches
1 conflict
0x106f80f5…d41b
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
3 conflicts on slot 0x8c560816ec…50447c
Audit this contract →
← previous block·next block →recent activity