← previous blocknext block →recent activity
Analyzing
Block #97,853,389
11 transactions · 10 stateful · 2026-08-21 07:49:35 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,853,389 · 11 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
4w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb1e37cb…90c9
0x34b655…2a6f
4 touches
1 conflict
0x232df012…c608
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x53ba75d8…354e
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
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
1 conflict on slot 0xdb1e37cb5e…7790c9
Audit this contract →
← previous block·next block →recent activity