← previous blocknext block →recent activity
Analyzing
Block #109,229,223
25 transactions · 21 stateful · 2026-09-30 04:41:06 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,229,223 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w010w111w012w113w214w015w118w321w022w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5441131b…1633
0x34b655…2a6f
8 touches
6 conflicts
0xe9457301…83cd
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x8725f80c…ff6d
0x1b6862…e19c
6 touches
3 conflicts
0x6110e17c…a54c
0xd32edf…ff58
5 touches
3 conflicts
0x336486a4…20bd
0x34b655…2a6f
4 touches
1 conflict
0x5e3014f0…b4e1
0x34b655…2a6f
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 0x5441131b75…cf1633
Audit this contract →
← previous block·next block →recent activity