← previous blocknext block →recent activity
Analyzing
Block #93,181,310
9 transactions · 9 stateful · 2026-08-04 22:35:20 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,181,310 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5110a94f…86d1
0x34b655…2a6f
4 touches
1 conflict
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0xb9694185…1504
0x34b655…2a6f
3 touches
1 conflict
0x3b730fde…abb5
0x34b655…2a6f
3 touches
1 conflict
0x6c33df7b…229a
0x065c9d…c394
2 touches
0 conflicts
0x7b54c896…0bc1
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
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 0x5110a94ff5…1e86d1
Audit this contract →
← previous block·next block →recent activity