← previous blocknext block →recent activity
Analyzing
Block #99,472,788
13 transactions · 13 stateful · 2026-08-27 00:32:42 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,472,788 · 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
2w03w04w17w29w310w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe736d40f…be6d
0x34b655…2a6f
10 touches
10 conflicts
0x33000c0a…82c3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
4 touches
1 conflict
0xdcebb2b8…5f18
0x34b655…2a6f
4 touches
1 conflict
0xf6deafb5…5c25
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
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
10 conflicts on slot 0xe736d40fd6…6fbe6d
Audit this contract →
← previous block·next block →recent activity