← previous blocknext block →recent activity
Analyzing
Block #99,866,624
15 transactions · 14 stateful · 2026-08-28 09:48:21 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,866,624 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w18w111w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0x9d6956d6…9681
0x34b655…2a6f
4 touches
1 conflict
0x272e6316…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x8765edd1…a7d5
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity