← previous blocknext block →recent activity
Analyzing
Block #79,022,185
15 transactions · 13 stateful · 2026-06-04 07:13:31 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,022,185 · 15 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
1w02w13w24w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x000203c4…e988
0x065c9d…c394
2 touches
0 conflicts
0xa1267d09…6b85
0x065c9d…c394
2 touches
0 conflicts
0x28b01e5f…ced5
0x2880ab…7b43
2 touches
0 conflicts
0x28b01e5f…ced6
0x2880ab…7b43
2 touches
0 conflicts
0x749437cf…2fc0
0x2880ab…7b43
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 0xc824469a90…af641c
Audit this contract →
← previous block·next block →recent activity