← previous blocknext block →recent activity
Analyzing
Block #93,064,234
21 transactions · 16 stateful · 2026-08-04 12:45:21 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,064,234 · 21 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
5w06w17w28w311w012w413w116w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
8 touches
6 conflicts
0x0a42683d…6f4f
0x34b655…2a6f
4 touches
1 conflict
0x453a271e…8768
0x34b655…2a6f
4 touches
1 conflict
0x6a9352a8…901b
0x34b655…2a6f
4 touches
1 conflict
0x70e3da66…674a
0x34b655…2a6f
4 touches
1 conflict
0x73820479…14f9
0x34b655…2a6f
4 touches
1 conflict
0x73c29f06…fffc
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity