← previous blocknext block →recent activity
Analyzing
Block #99,937,431
27 transactions · 22 stateful · 2026-08-28 15:45:09 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,937,431 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w010w015w116w117w019w122w223w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07bb3f5a…617e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd1203697…1ae0
0x40c49f…2af0
4 touches
1 conflict
0xb75d08b2…3e12
0x34b655…2a6f
4 touches
1 conflict
0xd4b8e8da…2e35
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xfd583065…9767
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
3 conflicts on slot 0x07bb3f5a12…2d617e
Audit this contract →
← previous block·next block →recent activity