← previous blocknext block →recent activity
Analyzing
Block #76,438,358
15 transactions · 12 stateful · 2026-05-23 08:09:31 UTC
Parallelism
87/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,438,358 · 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
2w03w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9b8ae99…32b4
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0xf9b8ae99…32b3
0x34b655…2a6f
4 touches
1 conflict
0x12d7f095…cfc8
0x1efe02…37d6
2 touches
0 conflicts
0x54f9bed3…03c4
0x1efe02…37d6
2 touches
0 conflicts
0x5d835479…b18e
0x1efe02…37d6
2 touches
0 conflicts
0xf8527368…409f
0x3bd359…433a
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
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 0xf9b8ae99dc…3532b4
Audit this contract →
← previous block·next block →recent activity