← previous blocknext block →recent activity
Analyzing
Block #93,243,062
12 transactions · 11 stateful · 2026-08-05 03:45:47 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,243,062 · 12 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
1w02w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x709c2293…6c55
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c56
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
2 touches
0 conflicts
0x5cc231f5…f1cd
0x2b46c0…1669
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 0x709c229336…a66c55
Audit this contract →
← previous block·next block →recent activity