← previous blocknext block →recent activity
Analyzing
Block #81,634,920
17 transactions · 14 stateful · 2026-06-16 09:45:01 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,634,920 · 17 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
1w02w03w14w26w311w012w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e3f9c0d…8a5f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xda5aae7c…774c
0xd32edf…ff58
3 touches
1 conflict
0x8c5f634b…63c5
0x065c9d…c394
3 touches
1 conflict
0xe3de55c2…ffe4
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0x0e3f9c0df4…b08a5f
Audit this contract →
← previous block·next block →recent activity