← previous blocknext block →recent activity
Analyzing
Block #98,538,162
16 transactions · 14 stateful · 2026-08-23 17:34:09 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,538,162 · 16 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
4w05w09w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c45a9d…3462
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0xeb88ed4e…a342
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a1
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…7212
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 0xc6c45a9d37…4d3462
Audit this contract →
← previous block·next block →recent activity