← previous blocknext block →recent activity
Analyzing
Block #98,024,330
14 transactions · 14 stateful · 2026-08-21 22:20:38 UTC
Parallelism
57/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,024,330 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x62023181…811e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x32cd523f…9885
0x34b655…2a6f
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0xe9e92bac…00ed
0x754704…b603
4 touches
1 conflict
0x68c08dd2…be14
0x99c7a7…8bf0
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity