← previous blocknext block →recent activity
Analyzing
Block #109,229,195
23 transactions · 20 stateful · 2026-09-30 04:40:57 UTC
Parallelism
74/100
Blocked
45%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,229,195 · 23 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
1w05w06w17w18w09w010w111w212w313w416w519w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x600fe6de…4c88
0x34b655…2a6f
8 touches
6 conflicts
0xe9457301…83cd
0x34b655…2a6f
8 touches
6 conflicts
0xfed0b5b6…4786
0x34b655…2a6f
8 touches
6 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0040
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0054
0x1b6862…e19c
4 touches
1 conflict
0x37009e5f…aa45
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
6 conflicts on slot 0x600fe6decf…8d4c88
Audit this contract →
← previous block·next block →recent activity