← previous blocknext block →recent activity
Analyzing
Block #98,451,335
16 transactions · 15 stateful · 2026-08-23 10:09:43 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,451,335 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w19w210w013w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2862d04…388c
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xdf8ce185…9061
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x49b0842d…0a93
0x34b655…2a6f
4 touches
1 conflict
0x50fb5da7…be0f
0x34b655…2a6f
4 touches
1 conflict
0x7db78f05…2895
0x34b655…2a6f
4 touches
1 conflict
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 0xd2862d04eb…53388c
Audit this contract →
← previous block·next block →recent activity