← previous blocknext block →recent activity
Analyzing
Block #97,817,763
14 transactions · 14 stateful · 2026-08-21 04:47:57 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,817,763 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c369b9c…e94d
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x640b1625…b02f
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x7316dc00…c16a
0x34b655…2a6f
4 touches
1 conflict
0x3cdf0dfb…1c93
0x34b655…2a6f
4 touches
1 conflict
0x45199977…2e99
0x34b655…2a6f
2 touches
0 conflicts
0x5281b9bf…129c
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 0x3c369b9ceb…45e94d
Audit this contract →
← previous block·next block →recent activity