← previous blocknext block →recent activity
Analyzing
Block #93,486,056
13 transactions · 13 stateful · 2026-08-06 00:07:29 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,486,056 · 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
1w02w03w16w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5031218f…deb8
0x34b655…2a6f
4 touches
1 conflict
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1b4fa1a0…7d7b
0x34b655…2a6f
2 touches
0 conflicts
0x2c390858…b1ed
0x34b655…2a6f
2 touches
0 conflicts
0x3187ceee…be8c
0x34b655…2a6f
2 touches
0 conflicts
0x3260d0da…4385
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 0x5031218f8d…91deb8
Audit this contract →
← previous block·next block →recent activity