← previous blocknext block →recent activity
Analyzing
Block #97,988,966
24 transactions · 20 stateful · 2026-08-21 19:22:10 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,988,966 · 24 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
1w03w08w09w112w013w015w116w120w122w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
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 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity