← previous blocknext block →recent activity
Analyzing
Block #79,419,731
18 transactions · 14 stateful · 2026-06-06 03:28:01 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,419,731 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w17w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cbd466f…1700
0x34b655…2a6f
4 touches
1 conflict
0x99e819a0…e5d0
0x34b655…2a6f
4 touches
1 conflict
0xd9d9b92f…6e55
0x34b655…2a6f
4 touches
1 conflict
0xa5b8f2bc…a274
0x34b655…2a6f
4 touches
1 conflict
0x99e819a0…e5d1
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
1 conflict on slot 0x7cbd466f36…791700
Audit this contract →
← previous block·next block →recent activity