← previous blocknext block →recent activity
Analyzing
Block #98,422,478
14 transactions · 14 stateful · 2026-08-23 07:44:32 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,422,478 · 14 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
1w02w14w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x0ce69307…e9a9
0x34b655…2a6f
4 touches
1 conflict
0x403a4649…d8be
0x34b655…2a6f
4 touches
1 conflict
0x39730b84…5e02
0x34b655…2a6f
2 touches
0 conflicts
0x3bc0a413…50b6
0x34b655…2a6f
2 touches
0 conflicts
0x4d4389b2…6e07
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 0x2c2db8e9ef…f4fdc7
Audit this contract →
← previous block·next block →recent activity