← previous blocknext block →recent activity
Analyzing
Block #99,317,447
8 transactions · 6 stateful · 2026-08-26 11:30:30 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,317,447 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c68d10b…8386
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x023b4f90…6425
0x34b655…2a6f
2 touches
0 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x26253352…1a75
0x34b655…2a6f
2 touches
0 conflicts
0x364d1d02…0528
0x34b655…2a6f
2 touches
0 conflicts
0x38b917a6…3464
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
1 conflict on slot 0x7c68d10b83…628386
Audit this contract →
← previous block·next block →recent activity