← previous blocknext block →recent activity
Analyzing
Block #93,487,359
17 transactions · 17 stateful · 2026-08-06 00:14:02 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,487,359 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w27w18w29w311w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3834f05…a4cf
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xc6b9bb4b…145a
0x34b655…2a6f
6 touches
3 conflicts
0xd676e291…3ecf
0x34b655…2a6f
6 touches
3 conflicts
0xb46bb9bf…deb7
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 0xa3834f0557…a4a4cf
Audit this contract →
← previous block·next block →recent activity