← previous blocknext block →recent activity
Analyzing
Block #80,369,832
18 transactions · 13 stateful · 2026-06-10 13:14:09 UTC
Parallelism
89/100
Blocked
15%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,369,832 · 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0c0048db…1a25
0x2a68ba…90c5
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0xe60a628c…d6d7
0x2a68ba…90c5
2 touches
0 conflicts
0xf853eb8e…401e
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
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 0x22e0cc1d4a…90ad04
Audit this contract →
← previous block·next block →recent activity