← previous blocknext block →recent activity
Analyzing
Block #93,573,281
10 transactions · 9 stateful · 2026-08-06 07:25:57 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,573,281 · 10 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
1w04w05w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf64c477b…5d19
0x34b655…2a6f
4 touches
1 conflict
0x913c477e…1427
0x34b655…2a6f
4 touches
1 conflict
0xc3aa7d62…056c
0x34b655…2a6f
4 touches
1 conflict
0xc3aa7d62…056d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd4
0x34b655…2a6f
4 touches
1 conflict
0xf4c9a0df…dcd5
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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
1 conflict on slot 0xf64c477be1…e55d19
Audit this contract →
← previous block·next block →recent activity