← previous blocknext block →recent activity
Analyzing
Block #99,878,781
19 transactions · 19 stateful · 2026-08-28 10:49:34 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,878,781 · 19 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
1w02w15w06w17w210w212w313w415w016w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6fcbbb7…2b31
0x34b655…2a6f
8 touches
6 conflicts
0xbd1a7493…7253
0x34b655…2a6f
6 touches
3 conflicts
0x64f1def5…eec0
0x34b655…2a6f
6 touches
3 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x207e9f25…4724
0x34b655…2a6f
4 touches
1 conflict
0x207e9f25…4725
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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 0xb6fcbbb7f3…142b31
Audit this contract →
← previous block·next block →recent activity