← previous blocknext block →recent activity
Analyzing
Block #99,869,940
26 transactions · 24 stateful · 2026-08-28 10:05:03 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,869,940 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w17w09w110w211w313w415w524w225w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad4e90b…33a5
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4f2e1481…fa91
0x34b655…2a6f
6 touches
3 conflicts
0xb9d9b740…9b29
0x34b655…2a6f
6 touches
3 conflicts
0x4fac394f…a439
0x34b655…2a6f
6 touches
3 conflicts
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0x07d94be1…7fa8
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
10 conflicts on slot 0xbad4e90ba6…2233a5
Audit this contract →
← previous block·next block →recent activity