← previous blocknext block →recent activity
Analyzing
Block #73,918,352
8 transactions · 7 stateful · 2026-05-11 15:51:59 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,918,352 · 8 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
1w02w13w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x711bee5b…c5ca
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xc9bdb46b…a42f
0xde22b2…7777
2 touches
1 conflict
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x5622b6ef…5ea9
0x34b655…2a6f
2 touches
0 conflicts
0x696cb728…4526
0x34b655…2a6f
2 touches
0 conflicts
0x7c30bd77…61ae
0x34b655…2a6f
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 0x711bee5b68…89c5ca
Audit this contract →
← previous block·next block →recent activity