← previous blocknext block →recent activity
Analyzing
Block #81,480,877
21 transactions · 18 stateful · 2026-06-15 16:39:06 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,480,877 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w09w110w011w113w214w315w418w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x38985dff…adaa
0x34b655…2a6f
4 touches
1 conflict
0x4e9b892b…6877
0x34b655…2a6f
4 touches
1 conflict
0x743061ce…a4ac
0x34b655…2a6f
4 touches
1 conflict
0x80c03bc4…03ef
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity