← previous blocknext block →recent activity
Analyzing
Block #73,991,746
16 transactions · 9 stateful · 2026-05-12 00:01:51 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,991,746 · 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
1w02w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x678d790b…6882
0x34b655…2a6f
4 touches
1 conflict
0xa15427f6…d932
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x590f1275…59bc
0xd32edf…ff58
3 touches
1 conflict
0x4c4487aa…8685
0x065c9d…c394
2 touches
0 conflicts
0x6ccbee17…1eed
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
0x065c9d…c394
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 0x2877f4400c…13c2c8
Audit this contract →
← previous block·next block →recent activity