← previous blocknext block →recent activity
Analyzing
Block #81,880,395
24 transactions · 17 stateful · 2026-06-17 13:00:44 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,880,395 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w28w39w410w511w012w113w217w118w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
12 touches
15 conflicts
0x830b63a6…8105
0x34b655…2a6f
6 touches
3 conflicts
0xfcb9138a…3830
0xc8689a…ee79
4 touches
1 conflict
0xa72e521d…f873
0x34b655…2a6f
4 touches
1 conflict
0xe994dc03…e3a6
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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: 0xaa7ee7ce…aff0e4
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity