← previous blocknext block →recent activity
Analyzing
Block #97,195,234
18 transactions · 18 stateful · 2026-08-18 23:49:53 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,195,234 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w28w311w012w413w215w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x3acc628e…e425
0x34b655…2a6f
6 touches
3 conflicts
0xeba56708…8cd7
0x2b46c0…1669
4 touches
1 conflict
0x317baac2…214e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x78cc79b1…334a
0x34b655…2a6f
4 touches
1 conflict
0x80f20e0a…d514
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
10 conflicts on slot 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity