← previous blocknext block →recent activity
Analyzing
Block #97,900,718
16 transactions · 16 stateful · 2026-08-21 11:53:14 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,900,718 · 16 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
1w03w04w15w06w07w18w09w110w113w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2528e717…2a22
0x34b655…2a6f
6 touches
3 conflicts
0xba1cd9c8…3f03
0x40c49f…2af0
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcc844ab5…4c6d
0x34b655…2a6f
4 touches
1 conflict
0xd898f3e8…29e1
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity