← previous blocknext block →recent activity
Analyzing
Block #109,004,180
28 transactions · 19 stateful · 2026-09-29 09:46:34 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,004,180 · 28 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
5w06w18w09w012w115w216w320w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1af9143d…be5c
0x851145…3f07
4 touches
1 conflict
0x934b15f1…b5a9
0x851145…3f07
4 touches
1 conflict
0x997ccc40…4dfd
0x3bd359…433a
2 touches
0 conflicts
0xb09bc9d0…f02f
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: Perpl
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity