← previous blocknext block →recent activity
Analyzing
Block #73,751,189
25 transactions · 17 stateful · 2026-05-10 21:13:57 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,751,189 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w012w113w014w115w016w017w119w221w022w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x0462262d…a368
0x34b655…2a6f
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x129ba946…48ab
0x34b655…2a6f
4 touches
1 conflict
0x1319ae2c…7f9a
0x34b655…2a6f
4 touches
1 conflict
0x23951077…539b
0x34b655…2a6f
4 touches
1 conflict
0x3638e1ad…ec0e
0x34b655…2a6f
4 touches
1 conflict
0x45b9e08c…a11b
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity