← previous blocknext block →recent activity
Analyzing
Block #98,550,364
13 transactions · 12 stateful · 2026-08-23 18:37:55 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,550,364 · 13 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
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2fe4c0e2…3052
0x1c8a33…d316
2 touches
0 conflicts
0x2b635ea7…4c03
0x34b655…2a6f
2 touches
0 conflicts
0x593b6913…4d2f
0x34b655…2a6f
2 touches
0 conflicts
0x68531239…e9a3
0x34b655…2a6f
2 touches
0 conflicts
0x6a2ca7be…18a8
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity