← previous blocknext block →recent activity
Analyzing
Block #97,817,657
16 transactions · 15 stateful · 2026-08-21 04:47:24 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,817,657 · 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
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa420374e…ae72
0x34b655…2a6f
4 touches
1 conflict
0x7316dc00…c16a
0x34b655…2a6f
4 touches
1 conflict
0x16981832…03f1
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x0416aa9a…86f9
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2afe4dba…3b17
0x34b655…2a6f
2 touches
0 conflicts
0x3b6e959d…158f
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 0xa420374e8a…b2ae72
Audit this contract →
← previous block·next block →recent activity