← previous blocknext block →recent activity
Analyzing
Block #93,364,321
35 transactions · 30 stateful · 2026-08-05 13:55:27 UTC
Parallelism
86/100
Blocked
63%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,364,321 · 35 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
1w02w14w25w36w49w011w112w213w314w415w016w118w219w326w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
10 touches
10 conflicts
0x50a45b29…54e2
0xd32edf…ff58
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x3d158563…8713
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
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: 0x91855e79…58ac7e
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity