← previous blocknext block →recent activity
Analyzing
Block #78,362,455
7 transactions · 6 stateful · 2026-06-01 05:54:35 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #78,362,455 · 7 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd869843e…99c9
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x4a667866…3348
0x065c9d…c394
2 touches
0 conflicts
0x4d1b789f…a6c0
0x065c9d…c394
2 touches
0 conflicts
0x6ae98e60…ebf7
0x065c9d…c394
2 touches
0 conflicts
0x849e2e96…1161
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity