← previous blocknext block →recent activity
Analyzing
Block #81,408,006
10 transactions · 9 stateful · 2026-06-15 08:33:28 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,408,006 · 10 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
1w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a58c77b…a8f4
0x34b655…2a6f
4 touches
1 conflict
0x7f93f2f0…6666
0x34b655…2a6f
4 touches
1 conflict
0x97785d36…2ac5
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xd0806a61…8350
0x34b655…2a6f
3 touches
1 conflict
0x7585925a…3f45
0x34b655…2a6f
2 touches
0 conflicts
0xadeea197…1c84
0x34b655…2a6f
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 0x5a58c77be4…f3a8f4
Audit this contract →
← previous block·next block →recent activity