← previous blocknext block →recent activity
Analyzing
Block #97,683,002
20 transactions · 14 stateful · 2026-08-20 17:26:38 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,683,002 · 20 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
1w04w05w16w17w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35b85d8e…1edd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x736c5b69…fb3f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x232e4f12…eb24
0x34b655…2a6f
2 touches
0 conflicts
0x2a4dfda9…cef5
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 0x35b85d8e2a…641edd
Audit this contract →
← previous block·next block →recent activity