← previous blocknext block →recent activity
Analyzing
Block #99,187,477
14 transactions · 13 stateful · 2026-08-26 00:36:34 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,187,477 · 14 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
3w08w110w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x168cce20…53ee
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xce74d807…8716
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x53de6eef…5084
0x34b655…2a6f
4 touches
1 conflict
0x4af3833e…f3bd
0x34b655…2a6f
2 touches
0 conflicts
0x6bab0076…422b
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
3 conflicts on slot 0x168cce2061…3353ee
Audit this contract →
← previous block·next block →recent activity