← previous blocknext block →recent activity
Analyzing
Block #93,566,648
13 transactions · 11 stateful · 2026-08-06 06:52:37 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,566,648 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x200ed648…912f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xebac0f82…a49c
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x139831ac…3151
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x200ed6482b…21912f
Audit this contract →
← previous block·next block →recent activity