← previous blocknext block →recent activity
Analyzing
Block #97,842,451
16 transactions · 15 stateful · 2026-08-21 06:52:51 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,842,451 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w08w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c7c1cc9…ac38
0x34b655…2a6f
4 touches
1 conflict
0x5e27ac10…7251
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7753b200…57a7
0x34b655…2a6f
4 touches
1 conflict
0x2560b0ef…aadf
0x34b655…2a6f
2 touches
0 conflicts
0x2ba79489…a23a
0x34b655…2a6f
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 0x7c7c1cc9a5…8fac38
Audit this contract →
← previous block·next block →recent activity