← previous blocknext block →recent activity
Analyzing
Block #74,353,607
12 transactions · 11 stateful · 2026-05-13 16:09:49 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,353,607 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x996de8c4…b3c2
0x065c9d…c394
3 touches
1 conflict
0xe6f02c67…1423
0x065c9d…c394
3 touches
1 conflict
0x194f2c02…19e6
0x2a68ba…90c5
2 touches
0 conflicts
0xfb083229…0138
0x2a68ba…90c5
2 touches
0 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
1 conflict on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity