← previous blocknext block →recent activity
Analyzing
Block #98,089,508
20 transactions · 15 stateful · 2026-08-22 03:48:36 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,089,508 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w09w112w013w116w118w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86eec3c2…0fa5
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
4 touches
1 conflict
0x12eabc4c…3d8a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
1 conflict on slot 0x86eec3c277…bf0fa5
Audit this contract →
← previous block·next block →recent activity