← previous blocknext block →recent activity
Analyzing
Block #99,196,745
20 transactions · 19 stateful · 2026-08-26 01:23:12 UTC
Parallelism
60/100
Blocked
37%
Avg conflicts / tx
0.85
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,196,745 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w011w113w214w316w417w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x056b3718…d91d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2202504e…fad0
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x8714eb4d…e184
0x34b655…2a6f
4 touches
1 conflict
0xabfdfd0e…20bf
0x34b655…2a6f
4 touches
1 conflict
0xb0f5d668…99ac
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 0x056b371879…83d91d
Audit this contract →
← previous block·next block →recent activity