← previous blocknext block →recent activity
Analyzing
Block #97,729,980
25 transactions · 20 stateful · 2026-08-20 21:25:01 UTC
Parallelism
84/100
Blocked
45%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,729,980 · 25 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
2w03w04w15w06w07w08w19w113w214w215w116w122w324w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe41626f9…dd93
0x34b655…2a6f
4 touches
1 conflict
0xf6c9bf9b…ac02
0x34b655…2a6f
4 touches
1 conflict
0xf875bac2…18bc
0x34b655…2a6f
4 touches
1 conflict
0xfaab1754…53be
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x0371cfce…4018
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 0xe41626f95d…d2dd93
Audit this contract →
← previous block·next block →recent activity