← previous blocknext block →recent activity
Analyzing
Block #98,013,104
28 transactions · 23 stateful · 2026-08-21 21:23:59 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,013,104 · 28 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
1w02w04w19w010w011w115w017w118w220w221w122w223w125w226w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x112f66a5…17d2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x077d58c3…8ed7
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
3 conflicts on slot 0x112f66a5ea…1017d2
Audit this contract →
← previous block·next block →recent activity