← previous blocknext block →recent activity
Analyzing
Block #93,439,021
11 transactions · 11 stateful · 2026-08-05 20:11:02 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,439,021 · 11 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
1w02w03w04w06w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedbde127…eccb
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f24
0x34b655…2a6f
4 touches
1 conflict
0x77f8d110…a65b
0x34b655…2a6f
4 touches
1 conflict
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdf6c3e51…c493
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
1 conflict on slot 0xedbde12768…8ceccb
Audit this contract →
← previous block·next block →recent activity