← previous blocknext block →recent activity
Analyzing
Block #73,753,530
17 transactions · 17 stateful · 2026-05-10 21:29:43 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,753,530 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w27w39w110w213w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
16 touches
28 conflicts
0x37ed0601…19f5
0x34b655…2a6f
12 touches
15 conflicts
0xd49762c9…1359
0x34b655…2a6f
10 touches
10 conflicts
0xfac43f12…b842
0x34b655…2a6f
8 touches
6 conflicts
0xedb848fe…6534
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a85cf3d…2868
0x34b655…2a6f
6 touches
3 conflicts
0x98961e60…28e1
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity