← previous blocknext block →recent activity
Analyzing
Block #97,818,146
15 transactions · 14 stateful · 2026-08-21 04:49:54 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,818,146 · 15 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
1w02w03w14w05w07w19w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b561ab0…637e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9e29ae1b…7b6c
0x34b655…2a6f
4 touches
1 conflict
0xa662186e…928a
0x34b655…2a6f
4 touches
1 conflict
0xbd3a099e…e0bb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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 0x2b561ab0d5…83637e
Audit this contract →
← previous block·next block →recent activity