← previous blocknext block →recent activity
Analyzing
Block #79,241,098
19 transactions · 17 stateful · 2026-06-05 07:33:14 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,241,098 · 19 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
2w03w16w210w012w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdc8b4bb…7bce
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x060728…d65c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6ef773ad…4d72
0x34b655…2a6f
4 touches
1 conflict
0x93aa4761…99e9
0x34b655…2a6f
4 touches
1 conflict
0x0f045139…1cc4
0x0a3323…0a3c
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 0xcdc8b4bbea…bd7bce
Audit this contract →
← previous block·next block →recent activity