← previous blocknext block →recent activity
Analyzing
Block #99,848,599
13 transactions · 13 stateful · 2026-08-28 08:17:24 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,848,599 · 13 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
2w04w06w17w28w39w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba00dff…ea1f
0x34b655…2a6f
8 touches
6 conflicts
0xf229fb25…39a5
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
4 touches
1 conflict
0x30ef1feb…1308
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
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 0xdba00dffd7…85ea1f
Audit this contract →
← previous block·next block →recent activity