← previous blocknext block →recent activity
Analyzing
Block #73,984,530
13 transactions · 8 stateful · 2026-05-11 23:13:12 UTC
Parallelism
85/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,984,530 · 13 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
3w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee230b20…5a0f
0x34b655…2a6f
4 touches
1 conflict
0x9d652ee8…83ca
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x03df3a18…58e7
0x34b655…2a6f
2 touches
0 conflicts
0x17dc7cd4…6e9d
0x34b655…2a6f
2 touches
0 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
2 touches
0 conflicts
0x2aef4269…ad47
0x34b655…2a6f
2 touches
0 conflicts
0xbbe5c289…487d
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 0xee230b202a…c05a0f
Audit this contract →
← previous block·next block →recent activity