← previous blocknext block →recent activity
Analyzing
Block #74,398,339
18 transactions · 16 stateful · 2026-05-13 21:07:37 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,398,339 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w312w014w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5202eeec…466f
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xc740dd24…9801
0x3bd359…433a
6 touches
3 conflicts
0xab621973…cc16
0x34b655…2a6f
6 touches
3 conflicts
0x44ad89ba…cf83
0x5df178…7777
6 touches
3 conflicts
0x00000000…0001
0x2c492d…444e
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
6 conflicts on slot 0x5202eeecc3…46466f
Audit this contract →
← previous block·next block →recent activity