← previous blocknext block →recent activity
Analyzing
Block #99,821,226
13 transactions · 12 stateful · 2026-08-28 05:58:53 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,821,226 · 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
1w02w14w05w16w28w39w412w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54fe7e99…7139
0x34b655…2a6f
8 touches
6 conflicts
0x74eb7f05…d11f
0x34b655…2a6f
8 touches
6 conflicts
0xd7668c61…55f8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x20b94f7c…2a9b
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x54fe7e9943…507139
Audit this contract →
← previous block·next block →recent activity