← previous blocknext block →recent activity
Analyzing
Block #108,612,041
21 transactions · 18 stateful · 2026-09-28 00:47:30 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,612,041 · 21 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
1w02w13w29w010w011w112w213w014w115w216w318w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0xe135588e…812f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c6
0x1b6862…e19c
6 touches
3 conflicts
0x1ace352e…96cb
0xd32edf…ff58
5 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
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 0x43e3decb93…7dbe40
Audit this contract →
← previous block·next block →recent activity