← previous blocknext block →recent activity
Analyzing
Block #74,427,540
18 transactions · 16 stateful · 2026-05-14 00:21:55 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,427,540 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w111w014w115w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbad68552…e6bf
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbb12db23…857e
0x34b655…2a6f
6 touches
3 conflicts
0x4e39aafd…796e
0x34b655…2a6f
4 touches
1 conflict
0x816881fb…e436
0x34b655…2a6f
4 touches
1 conflict
0xa486f342…64d5
0x34b655…2a6f
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x06c10d86…6883
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 0xbad6855239…f0e6bf
Audit this contract →
← previous block·next block →recent activity