← previous blocknext block →recent activity
Analyzing
Block #93,923,608
16 transactions · 14 stateful · 2026-08-07 12:47:37 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,923,608 · 16 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
2w07w08w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a114ce…40e2
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
0xa3f6f7c8…2436
0x34b655…2a6f
4 touches
1 conflict
0x6eff5416…605d
0xea1b8e…c5ec
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 0xa5a114ceb5…3e40e2
Audit this contract →
← previous block·next block →recent activity