← previous blocknext block →recent activity
Analyzing
Block #108,672,174
18 transactions · 16 stateful · 2026-09-28 05:50:21 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,672,174 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w110w111w212w313w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x766b47a3…87be
0x34b655…2a6f
10 touches
10 conflicts
0xe5735dd3…baa3
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
6 touches
3 conflicts
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
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
10 conflicts on slot 0x766b47a3cc…0787be
Audit this contract →
← previous block·next block →recent activity