← previous blocknext block →recent activity
Analyzing
Block #93,856,267
13 transactions · 11 stateful · 2026-08-07 07:08:36 UTC
Parallelism
85/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,856,267 · 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
1w02w13w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c5968c7…708a
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x310e7923…a70d
0xd32edf…ff58
3 touches
1 conflict
0x04504abd…1819
0x065c9d…c394
2 touches
0 conflicts
0x480daf1b…be95
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
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 0x1c5968c79b…c1708a
Audit this contract →
← previous block·next block →recent activity