← previous blocknext block →recent activity
Analyzing
Block #97,545,086
22 transactions · 20 stateful · 2026-08-20 05:41:58 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,545,086 · 22 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
1w02w03w15w06w29w011w312w113w215w416w120w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea1d91a3…b583
0x34b655…2a6f
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x33a247…6221
4 touches
1 conflict
0x6ef7ecd7…4e35
0x33a247…6221
4 touches
1 conflict
0x99df0a1e…5458
0x33a247…6221
4 touches
1 conflict
0x4d1e3e31…edf8
0x3bd359…433a
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
6 conflicts on slot 0xea1d91a39b…86b583
Audit this contract →
← previous block·next block →recent activity