← previous blocknext block →recent activity
Analyzing
Block #80,824,090
18 transactions · 16 stateful · 2026-06-12 15:43:36 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,824,090 · 18 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
1w02w14w05w16w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0x19be00ce…7a97
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x46173284…6407
0x34b655…2a6f
4 touches
1 conflict
0xa95c4e57…635e
0xc8689a…ee79
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 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 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity