← previous blocknext block →recent activity
Analyzing
Block #97,564,867
18 transactions · 17 stateful · 2026-08-20 07:22:54 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,564,867 · 18 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
2w04w05w16w17w211w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dc86774…166a
0x34b655…2a6f
8 touches
6 conflicts
0x5cfec795…7c0e
0x34b655…2a6f
4 touches
1 conflict
0x88ef4184…503b
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x41ea893f…1c6c
0x065c9d…c394
2 touches
0 conflicts
0x4501b5ae…2035
0x065c9d…c394
2 touches
0 conflicts
0x77ed432f…fa04
0x065c9d…c394
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
6 conflicts on slot 0x1dc86774a8…36166a
Audit this contract →
← previous block·next block →recent activity