← previous blocknext block →recent activity
Analyzing
Block #99,619,720
15 transactions · 14 stateful · 2026-08-27 12:58:49 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,619,720 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w011w112w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb856d1a1…1f18
0x34b655…2a6f
4 touches
1 conflict
0xe57afd08…90bd
0x34b655…2a6f
4 touches
1 conflict
0x23c1dd54…8fdf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x67a56c8b…f955
0x34b655…2a6f
2 touches
0 conflicts
0x7fe8b5d8…3e49
0x34b655…2a6f
2 touches
0 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
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
1 conflict on slot 0xb856d1a127…bf1f18
Audit this contract →
← previous block·next block →recent activity