← previous blocknext block →recent activity
Analyzing
Block #97,841,987
21 transactions · 19 stateful · 2026-08-21 06:50:30 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,841,987 · 21 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
2w03w14w06w17w28w29w010w111w012w318w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf8a1de57…8f84
0x34b655…2a6f
4 touches
1 conflict
0xe4deb662…1ee0
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2528e717…2a22
0x34b655…2a6f
4 touches
1 conflict
0x3037116c…a62d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x469dac8d…3411
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 0xf8a1de5701…d68f84
Audit this contract →
← previous block·next block →recent activity