← previous blocknext block →recent activity
Analyzing
Block #108,576,300
23 transactions · 21 stateful · 2026-09-27 21:47:34 UTC
Parallelism
87/100
Blocked
24%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,576,300 · 23 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
4w05w09w011w013w014w115w116w221w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4292a836…9ed5
0x34b655…2a6f
4 touches
1 conflict
0x8da42975…b56f
0x34b655…2a6f
4 touches
1 conflict
0xa23b9051…392f
0x34b655…2a6f
4 touches
1 conflict
0xc2374606…93f7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
1 conflict on slot 0x4292a8361f…a09ed5
Audit this contract →
← previous block·next block →recent activity