← previous blocknext block →recent activity
Analyzing
Block #97,827,633
18 transactions · 16 stateful · 2026-08-21 05:37:49 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,827,633 · 18 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
1w02w15w06w17w08w19w110w213w014w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0xe2341c33…934c
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x59939ccc…8922
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00096307…5a3d
0x34b655…2a6f
4 touches
1 conflict
0x2407edc1…f2c8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xe188ad90a8…5bd23f
Audit this contract →
← previous block·next block →recent activity