← previous blocknext block →recent activity
Analyzing
Block #93,576,592
24 transactions · 24 stateful · 2026-08-06 07:42:36 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,576,592 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w06w17w28w39w410w511w612w615w118w123w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
12 touches
15 conflicts
0xe9ef16e7…2d22
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd877e706…e9c0
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x18de67b0…bf35
0x34b655…2a6f
6 touches
3 conflicts
0x78860c4f…cade
0x34b655…2a6f
4 touches
1 conflict
0x7aae9795…06ed
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
15 conflicts on slot 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity