← previous blocknext block →recent activity
Analyzing
Block #93,327,158
21 transactions · 19 stateful · 2026-08-05 10:48:36 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,327,158 · 21 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
6w07w18w09w113w015w116w217w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
4 touches
1 conflict
0xf73968e2…7d50
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x39ab5ddf…8a72
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe74deb99…9e5b
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: 0x91855e79…58ac7e
1 conflict on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity