← previous blocknext block →recent activity
Analyzing
Block #99,246,428
9 transactions · 9 stateful · 2026-08-26 05:33:10 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,246,428 · 9 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
1w02w13w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb748c8b…c9ec
0x34b655…2a6f
6 touches
3 conflicts
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
2 touches
0 conflicts
0x3b86caa0…a2a9
0x34b655…2a6f
2 touches
0 conflicts
0x676f9f01…a8ac
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 0xcb748c8bbb…8dc9ec
Audit this contract →
← previous block·next block →recent activity