← previous blocknext block →recent activity
Analyzing
Block #74,945,045
16 transactions · 9 stateful · 2026-05-16 10:00:04 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,945,045 · 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
6w07w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc683230…6df3
0x34b655…2a6f
4 touches
1 conflict
0x90687d94…b524
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x5939acf5…179f
0x96b79e…d00a
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x37d49489…9309
0x34b655…2a6f
2 touches
0 conflicts
0x4f483049…3cc7
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 0xdc683230c0…216df3
Audit this contract →
← previous block·next block →recent activity