← previous blocknext block →recent activity
Analyzing
Block #98,571,460
21 transactions · 19 stateful · 2026-08-23 20:28:05 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,571,460 · 21 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
4w06w07w112w114w215w016w118w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe62e1553…ed4b
0x34b655…2a6f
4 touches
1 conflict
0xf3981be5…2c47
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x1408a100…f721
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x7065ef11…461a
0x34b655…2a6f
4 touches
1 conflict
0x94789504…4524
0x34b655…2a6f
4 touches
1 conflict
0x94789504…4525
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
1 conflict on slot 0xe62e1553de…17ed4b
Audit this contract →
← previous block·next block →recent activity