← previous blocknext block →recent activity
Analyzing
Block #98,537,993
16 transactions · 15 stateful · 2026-08-23 17:33:15 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,537,993 · 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
2w03w04w19w011w112w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xb685c1fe…aef1
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x55cbbb33…467d
0x34b655…2a6f
4 touches
1 conflict
0x5922eaf1…dc70
0x57ea24…2cec
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 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity