← previous blocknext block →recent activity
Analyzing
Block #77,237,004
18 transactions · 16 stateful · 2026-05-27 00:49:54 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,237,004 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w29w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x7170c140…36bc
0x34b655…2a6f
4 touches
1 conflict
0xe8aab7db…a319
0xa6afd3…d132
4 touches
1 conflict
0x426a7c9f…bd77
0x065c9d…c394
4 touches
1 conflict
0xf9ae8e25…52ad
0x065c9d…c394
3 touches
1 conflict
0x3da78bb9…6ebd
0x065c9d…c394
3 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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity