← previous blocknext block →recent activity
Analyzing
Block #81,876,188
18 transactions · 14 stateful · 2026-06-17 12:32:40 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,876,188 · 18 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
1w02w14w08w09w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0xa4dae615…1cf8
0x34b655…2a6f
6 touches
3 conflicts
0x2da28f3b…cc6e
0x34b655…2a6f
6 touches
3 conflicts
0x309ef367…e8a1
0x34b655…2a6f
4 touches
1 conflict
0x3214fb6a…0f14
0x34b655…2a6f
4 touches
1 conflict
0xdc746738…0698
0x34b655…2a6f
4 touches
1 conflict
0x53b4ef2b…8a05
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity