← previous blocknext block →recent activity
Analyzing
Block #98,387,853
32 transactions · 25 stateful · 2026-08-23 04:50:19 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,387,853 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w111w012w113w215w018w019w120w221w324w425w226w027w131w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98834cc0…6c23
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x9cc55b14…fae5
0xd32edf…ff58
5 touches
3 conflicts
0x0cf2a2bb…7773
0x34b655…2a6f
4 touches
1 conflict
0x17ff2059…ddb4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
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
3 conflicts on slot 0x98834cc09c…676c23
Audit this contract →
← previous block·next block →recent activity