← previous blocknext block →recent activity
Analyzing
Block #93,314,727
16 transactions · 13 stateful · 2026-08-05 09:46:06 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,314,727 · 16 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
7w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xf394e6ad…f568
0x34b655…2a6f
4 touches
1 conflict
0xfaff8d68…b160
0x0a4fcb…a602
2 touches
0 conflicts
0xfaff8d68…b165
0x0a4fcb…a602
2 touches
0 conflicts
0xfaff8d68…b166
0x0a4fcb…a602
2 touches
0 conflicts
0xfaff8d68…b168
0x0a4fcb…a602
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity