← previous blocknext block →recent activity
Analyzing
Block #109,176,756
8 transactions · 8 stateful · 2026-09-30 00:17:01 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,176,756 · 8 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
1w02w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xd0ec60a1…d242
0x1b6862…e19c
4 touches
1 conflict
0x866110ca…7080
0x34b655…2a6f
4 touches
1 conflict
0xe068cf01…a40c
0x34b655…2a6f
4 touches
1 conflict
0xe763a93c…e90b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x40f95328…831b
0xd32edf…ff58
3 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity