← previous blocknext block →recent activity
Analyzing
Block #93,243,257
13 transactions · 12 stateful · 2026-08-05 03:46:45 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,243,257 · 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
6w07w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67b129b6…1ff7
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c55
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c56
0x34b655…2a6f
4 touches
1 conflict
0xd79e9cac…9f72
0x34b655…2a6f
4 touches
1 conflict
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x0d4188a3…dd5d
0x34b655…2a6f
3 touches
1 conflict
0x55898fed…c787
0x34b655…2a6f
2 touches
0 conflicts
0x959e17ee…0830
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 0x67b129b670…5a1ff7
Audit this contract →
← previous block·next block →recent activity