← previous blocknext block →recent activity
Analyzing
Block #99,355,656
10 transactions · 9 stateful · 2026-08-26 14:42:47 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,355,656 · 10 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
3w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0xce6d2591…ddeb
0x34b655…2a6f
3 touches
1 conflict
0x006c3b86…59a9
0x34b655…2a6f
3 touches
1 conflict
0x341567b6…0780
0x0a3323…0a3c
2 touches
0 conflicts
0xf139e227…5fea
0x0a3323…0a3c
2 touches
0 conflicts
0xa060b594…669d
0x754704…b603
2 touches
0 conflicts
0xb741db73…adbd
0x754704…b603
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity