← previous blocknext block →recent activity
Analyzing
Block #75,542,651
15 transactions · 9 stateful · 2026-05-19 04:41:16 UTC
Parallelism
87/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,542,651 · 15 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
6w07w110w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0xede5654e…4584
0x065c9d…c394
3 touches
1 conflict
0xf0b9524a…a1e4
0x065c9d…c394
3 touches
1 conflict
0x80dee4bf…51d8
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x291294a9…e304
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x59f1c822…6f02
0x065c9d…c394
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 0x5086c64a56…bb28ba
Audit this contract →
← previous block·next block →recent activity