← previous blocknext block →recent activity
Analyzing
Block #108,646,564
13 transactions · 13 stateful · 2026-09-28 03:41:23 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,646,564 · 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
1w06w17w28w211w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x845b769c…d13e
0x34b655…2a6f
4 touches
1 conflict
0xb17fc29f…bfad
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb9ee83b9…e0bf
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x186d3d89…4098
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
1 conflict on slot 0x845b769c6e…83d13e
Audit this contract →
← previous block·next block →recent activity