← previous blocknext block →recent activity
Analyzing
Block #98,575,746
25 transactions · 24 stateful · 2026-08-23 20:50:30 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,575,746 · 25 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
2w03w17w011w012w115w019w121w222w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e6de23…d3d5
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
4 touches
1 conflict
0x21782480…a6f8
0x34b655…2a6f
4 touches
1 conflict
0x299c0f04…09cf
0x34b655…2a6f
4 touches
1 conflict
0x307bf2c4…72fb
0x34b655…2a6f
4 touches
1 conflict
0x312e4698…54c0
0x34b655…2a6f
4 touches
1 conflict
0x3ca268be…8865
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
1 conflict on slot 0x01e6de23f4…68d3d5
Audit this contract →
← previous block·next block →recent activity