← previous blocknext block →recent activity
Analyzing
Block #98,458,062
18 transactions · 17 stateful · 2026-08-23 10:43:44 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,458,062 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w28w39w113w014w115w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x23a95727…f01e
0x40c49f…2af0
4 touches
1 conflict
0x12e7c471…901c
0x34b655…2a6f
4 touches
1 conflict
0x2eca27fa…dba4
0x34b655…2a6f
4 touches
1 conflict
0x3a2848d0…55dd
0x34b655…2a6f
4 touches
1 conflict
0x9816fc81…4f3d
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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity