← previous blocknext block →recent activity
Analyzing
Block #79,123,510
19 transactions · 16 stateful · 2026-06-04 18:29:13 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,123,510 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w214w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc33eb900…5632
0xd32edf…ff58
5 touches
3 conflicts
0x1f75e06e…c530
0x34b655…2a6f
4 touches
1 conflict
0x3a169d09…8c90
0x34b655…2a6f
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x6c73c136…2ca1
0x34b655…2a6f
4 touches
1 conflict
0x726e208b…f3ca
0x34b655…2a6f
4 touches
1 conflict
0x730c8155…0856
0x34b655…2a6f
4 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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity