← previous blocknext block →recent activity
Analyzing
Block #98,561,434
13 transactions · 12 stateful · 2026-08-23 19:35:41 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,561,434 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w110w011w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xb4b350eb…8c96
0x34b655…2a6f
4 touches
1 conflict
0x9c3004b2…5421
0x34b655…2a6f
2 touches
0 conflicts
0xb245fe36…d765
0x34b655…2a6f
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
3 conflicts on slot 0xadac4a860c…a3c2bc
Audit this contract →
← previous block·next block →recent activity