← previous blocknext block →recent activity
Analyzing
Block #99,487,087
20 transactions · 17 stateful · 2026-08-27 01:44:44 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,487,087 · 20 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
4w05w06w17w28w09w111w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40afcb37…764e
0x34b655…2a6f
8 touches
6 conflicts
0x7531533e…ad6e
0x34b655…2a6f
8 touches
6 conflicts
0x8ec95f2b…f4d7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0x74e46435…fdcd
0x34b655…2a6f
4 touches
1 conflict
0x8b7fe709…9d99
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 0x40afcb378f…37764e
Audit this contract →
← previous block·next block →recent activity