← previous blocknext block →recent activity
Analyzing
Block #98,562,857
68 transactions · 68 stateful · 2026-08-23 19:43:02 UTC
Parallelism
97/100
Blocked
1%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,562,857 · 68 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
66w067w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x34ad8535…e1d3
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x47ee9f76…8def
0x34b655…2a6f
2 touches
0 conflicts
0x1686502b…a1d2
0x3bd359…433a
2 touches
0 conflicts
0x00000000…004b
0x80c745…7210
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity