← previous blocknext block →recent activity
Analyzing
Block #109,176,960
13 transactions · 9 stateful · 2026-09-30 00:18:02 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,176,960 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbefdde57…cd0e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x9c0dc7df…0562
0x34b655…2a6f
4 touches
1 conflict
0x6235638c…6438
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
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
3 conflicts on slot 0xbefdde5725…1dcd0e
Audit this contract →
← previous block·next block →recent activity