← previous blocknext block →recent activity
Analyzing
Block #109,169,628
20 transactions · 16 stateful · 2026-09-29 23:41:09 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,169,628 · 20 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
2w03w14w05w18w09w010w011w112w213w314w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb22e4cdf…5fbd
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
8 touches
6 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x6235638c…6438
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0xb22e4cdfd7…a35fbd
Audit this contract →
← previous block·next block →recent activity