← previous blocknext block →recent activity
Analyzing
Block #98,604,973
15 transactions · 14 stateful · 2026-08-23 23:22:41 UTC
Parallelism
87/100
Blocked
7%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,604,973 · 15 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
5w06w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x9654e93b…e153
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x5ea77515…8e72
0x34b655…2a6f
4 touches
1 conflict
0x887e9867…1258
0x34b655…2a6f
3 touches
1 conflict
0x173df5ef…3917
0x34b655…2a6f
2 touches
0 conflicts
0x24bb46f7…3853
0x34b655…2a6f
2 touches
0 conflicts
0x31532dc6…db47
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity