← previous blocknext block →recent activity
Analyzing
Block #98,384,998
16 transactions · 14 stateful · 2026-08-23 04:35:58 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,384,998 · 16 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
1w08w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4890bce6…4d57
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4f3a6b4a…3819
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x15698ac9…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x1e1541ce…9e06
0x34b655…2a6f
2 touches
0 conflicts
0x1f27d6ba…892e
0x34b655…2a6f
2 touches
0 conflicts
0x3a9149df…72e0
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 0x4890bce649…634d57
Audit this contract →
← previous block·next block →recent activity