← previous blocknext block →recent activity
Analyzing
Block #80,704,047
19 transactions · 17 stateful · 2026-06-12 02:23:03 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,704,047 · 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
1w02w14w05w18w212w013w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1504aa7b…24ad
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xfe1362cf…bb85
0xa6afd3…d132
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xc9b1f1c3…f5cd
0xa6afd3…d132
5 touches
3 conflicts
0x4797aea6…c381
0xa6afd3…d132
5 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0xa6afd386…b0d132
3 conflicts on slot 0x1504aa7bc8…d024ad
Audit this contract →
← previous block·next block →recent activity