← previous blocknext block →recent activity
Analyzing
Block #98,431,244
16 transactions · 15 stateful · 2026-08-23 08:28:38 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,431,244 · 16 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x30422ec1…0a83
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x077d58c3…8ed7
0x34b655…2a6f
2 touches
0 conflicts
0x12021baf…a90a
0x34b655…2a6f
2 touches
0 conflicts
0x2f3f3ea3…f5f0
0x34b655…2a6f
2 touches
0 conflicts
0x3e157648…12f8
0x34b655…2a6f
2 touches
0 conflicts
0x51c8b4fa…003e
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity