← previous blocknext block →recent activity
Analyzing
Block #74,284,620
18 transactions · 14 stateful · 2026-05-13 08:30:59 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,284,620 · 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
1w05w06w18w113w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xb9d2cf20…a668
0x34b655…2a6f
6 touches
3 conflicts
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 conflicts
0xfe3b9476…2e67
0x34b655…2a6f
6 touches
3 conflicts
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity