← previous blocknext block →recent activity
Analyzing
Block #93,853,255
8 transactions · 7 stateful · 2026-08-07 06:53:28 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,853,255 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b96adb2…ba5d
0x34b655…2a6f
4 touches
1 conflict
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x02693e83…54be
0x34b655…2a6f
2 touches
0 conflicts
0x030fc94e…68fb
0x34b655…2a6f
2 touches
0 conflicts
0x0e5211d5…fbfe
0x34b655…2a6f
2 touches
0 conflicts
0x2977992f…fd28
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x388114fc…db6c
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 0x2b96adb26f…a6ba5d
Audit this contract →
← previous block·next block →recent activity