← previous blocknext block →recent activity
Analyzing
Block #98,452,058
18 transactions · 17 stateful · 2026-08-23 10:13:21 UTC
Parallelism
83/100
Blocked
12%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,452,058 · 18 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
1w02w14w09w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56ae218…1fc5
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xaa39f808…76a2
0x34b655…2a6f
4 touches
1 conflict
0x9fc6ea79…e2dc
0x34b655…2a6f
4 touches
1 conflict
0x1fd77335…9120
0x34b655…2a6f
2 touches
0 conflicts
0x37202e35…3f71
0x34b655…2a6f
2 touches
0 conflicts
0x3ff152f4…7b47
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
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 0xa56ae21853…e31fc5
Audit this contract →
← previous block·next block →recent activity