← previous blocknext block →recent activity
Analyzing
Block #97,818,378
16 transactions · 16 stateful · 2026-08-21 04:51:05 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,818,378 · 16 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
1w04w05w16w17w28w09w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7316dc00…c16a
0x34b655…2a6f
4 touches
1 conflict
0x06f80293…28ce
0x34b655…2a6f
4 touches
1 conflict
0x921893c3…b9b6
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
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 0x7316dc00d3…b5c16a
Audit this contract →
← previous block·next block →recent activity