← previous blocknext block →recent activity
Analyzing
Block #99,983,828
11 transactions · 11 stateful · 2026-08-28 19:38:54 UTC
Parallelism
55/100
Blocked
45%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,983,828 · 11 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
2w03w14w05w26w38w49w010w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x82dbd1ce…c027
0x34b655…2a6f
6 touches
3 conflicts
0xef048f92…572b
0x34b655…2a6f
6 touches
3 conflicts
0x02373c43…3cb3
0x34b655…2a6f
6 touches
3 conflicts
0x41469894…598f
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x53f7214d…8ec6
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
3 conflicts on slot 0x82dbd1ce84…b1c027
Audit this contract →
← previous block·next block →recent activity