← previous blocknext block →recent activity
Analyzing
Block #97,358,057
8 transactions · 7 stateful · 2026-08-19 13:36:40 UTC
Parallelism
50/100
Blocked
43%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,358,057 · 8 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
1w02w14w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d863b2f…bd28
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb45ccbf6…4112
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x3df0422c…fd38
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd39
0x34b655…2a6f
2 touches
0 conflicts
0x6083af24…a0df
0x34b655…2a6f
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 0x5d863b2fa9…a7bd28
Audit this contract →
← previous block·next block →recent activity