← previous blocknext block →recent activity
Analyzing
Block #73,328,095
16 transactions · 14 stateful · 2026-05-08 22:07:38 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
1.13
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,328,095 · 16 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9114f…44c2
0x34b655…2a6f
8 touches
6 conflicts
0x42446806…33dd
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x5d70606a…1d53
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity