← previous blocknext block →recent activity
Analyzing
Block #74,632,205
16 transactions · 13 stateful · 2026-05-14 23:12:02 UTC
Parallelism
56/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,632,205 · 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
1w02w15w06w17w211w012w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0eac6378…36f4
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0x070a562a…8147
0x34b655…2a6f
7 touches
6 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
6 touches
3 conflicts
0x2d8c9ff9…8b1d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity