← previous blocknext block →recent activity
Analyzing
Block #98,654,560
20 transactions · 20 stateful · 2026-08-24 03:40:43 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,654,560 · 20 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
1w02w14w05w17w08w110w013w214w215w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedee7e09…6888
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x15b15bca…1913
0x34b655…2a6f
4 touches
1 conflict
0x1e9a82ab…d631
0x34b655…2a6f
4 touches
1 conflict
0x6b2f61c7…0ef6
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x92b1c2aa…542d
0x34b655…2a6f
4 touches
1 conflict
0x93a29008…b89e
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
6 conflicts on slot 0xedee7e090f…056888
Audit this contract →
← previous block·next block →recent activity