← previous blocknext block →recent activity
Analyzing
Block #79,250,224
8 transactions · 7 stateful · 2026-06-05 08:34:14 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #79,250,224 · 8 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64461c10…e86d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x0ab26740…d451
0x2ab50b…5c41
2 touches
0 conflicts
0x0b166071…3ac4
0x2ab50b…5c41
2 touches
0 conflicts
0x0e743da4…0e5f
0x2ab50b…5c41
2 touches
0 conflicts
0x0ed5b6a1…253b
0x2ab50b…5c41
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 0x64461c10d4…d1e86d
Audit this contract →
← previous block·next block →recent activity