← previous blocknext block →recent activity
Analyzing
Block #108,655,537
17 transactions · 16 stateful · 2026-09-28 04:26:33 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,655,537 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc856ff11…2b9c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0f511ea2…39a1
0x34b655…2a6f
4 touches
1 conflict
0x970da48a…345b
0x34b655…2a6f
4 touches
1 conflict
0xa73f4add…2c29
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
2 touches
0 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
1 conflict on slot 0xc856ff1166…d02b9c
Audit this contract →
← previous block·next block →recent activity