← previous blocknext block →recent activity
Analyzing
Block #98,019,724
32 transactions · 22 stateful · 2026-08-21 21:57:18 UTC
Parallelism
91/100
Blocked
36%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,019,724 · 32 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
1w03w14w05w06w110w016w017w120w022w123w124w230w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d3436c8…7ce0
0x34b655…2a6f
6 touches
3 conflicts
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4b5dff54…45ec
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 0x5d3436c8ab…fd7ce0
Audit this contract →
← previous block·next block →recent activity