← previous blocknext block →recent activity
Analyzing
Block #97,901,494
16 transactions · 13 stateful · 2026-08-21 11:57:12 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,901,494 · 16 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
2w03w04w15w29w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x074c08f8…fb56
0x34b655…2a6f
4 touches
1 conflict
0x4c20d376…0819
0x34b655…2a6f
4 touches
1 conflict
0xd3894c9c…5a6d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 conflicts
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity