← previous blocknext block →recent activity
Analyzing
Block #98,260,573
20 transactions · 18 stateful · 2026-08-22 18:09:57 UTC
Parallelism
90/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,260,573 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w08w09w110w111w012w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3d41c87…c724
0x34b655…2a6f
4 touches
1 conflict
0xe3d7c1f1…1f50
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xfc5c96d2…af3c
0xe52b14…7230
3 touches
1 conflict
0xad2bb81f…4d6b
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
1 conflict on slot 0xd3d41c873f…e6c724
Audit this contract →
← previous block·next block →recent activity