← previous blocknext block →recent activity
Analyzing
Block #79,241,307
21 transactions · 19 stateful · 2026-06-05 07:34:38 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,241,307 · 21 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
1w05w06w112w115w116w017w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x55b6a001…1e7a
0x34b655…2a6f
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0x93aa4761…99e9
0x34b655…2a6f
4 touches
1 conflict
0xcdc8b4bb…7bce
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
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