← previous blocknext block →recent activity
Analyzing
Block #97,690,960
23 transactions · 21 stateful · 2026-08-20 18:06:57 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,690,960 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w09w110w111w213w014w115w016w218w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd254ae3…5b9f
0x34b655…2a6f
4 touches
1 conflict
0xe429e4c9…9510
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x157b6348…8604
0x34b655…2a6f
4 touches
1 conflict
0x27ed3ff6…6ea1
0x34b655…2a6f
4 touches
1 conflict
0x41be9e75…9773
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xcd254ae3bd…7b5b9f
Audit this contract →
← previous block·next block →recent activity