← previous blocknext block →recent activity
Analyzing
Block #98,662,681
13 transactions · 12 stateful · 2026-08-24 04:23:15 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,662,681 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w07w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb20094ed…0fef
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x104887dc…9894
0x34b655…2a6f
2 touches
0 conflicts
0x1d731f70…4557
0x34b655…2a6f
2 touches
0 conflicts
0x2671d7e0…3969
0x34b655…2a6f
2 touches
0 conflicts
0x272dc9b8…1b58
0x34b655…2a6f
2 touches
0 conflicts
0x37379933…2402
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 0xb20094edc6…ed0fef
Audit this contract →
← previous block·next block →recent activity