← previous blocknext block →recent activity
Analyzing
Block #109,137,417
21 transactions · 18 stateful · 2026-09-29 20:58:39 UTC
Parallelism
76/100
Blocked
28%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #109,137,417 · 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
1w03w04w05w115w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x013bb37b…eb4a
0x1b6862…e19c
8 touches
6 conflicts
0x6a9c8c76…d792
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0009
0x125f12…a50b
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0052
0x1b6862…e19c
2 touches
0 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: 0x125f12a1…cda50b
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity