← previous blocknext block →recent activity
Analyzing
Block #93,485,449
20 transactions · 20 stateful · 2026-08-06 00:04:26 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,485,449 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w17w28w010w211w312w113w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb67817f3…bd57
0x34b655…2a6f
8 touches
6 conflicts
0x8cd191b6…2397
0x34b655…2a6f
8 touches
6 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x4e8c6085…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xb67817f34d…bebd57
Audit this contract →
← previous block·next block →recent activity