← previous blocknext block →recent activity
Analyzing
Block #93,314,734
21 transactions · 20 stateful · 2026-08-05 09:46:09 UTC
Parallelism
76/100
Blocked
30%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,314,734 · 21 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
4w010w011w112w114w215w317w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x176ce0ad…6382
0x34b655…2a6f
4 touches
1 conflict
0x17dd227b…1380
0x34b655…2a6f
4 touches
1 conflict
0x22c6ecc6…c70d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
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 0x861e5aeffa…5cd32c
Audit this contract →
← previous block·next block →recent activity