← previous blocknext block →recent activity
Analyzing
Block #98,747,937
17 transactions · 14 stateful · 2026-08-24 11:38:09 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,747,937 · 17 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
2w03w05w17w19w010w112w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e901144…309e
0x34b655…2a6f
4 touches
1 conflict
0x6d8ad688…4bf5
0xa6afd3…d132
4 touches
1 conflict
0xeda104e5…d422
0x34b655…2a6f
4 touches
1 conflict
0xe62e1553…ed4b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
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 0x1e90114498…36309e
Audit this contract →
← previous block·next block →recent activity