← previous blocknext block →recent activity
Analyzing
Block #81,094,924
16 transactions · 11 stateful · 2026-06-13 21:49:03 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,094,924 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa4f19eae…f468
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x29df973e…2671
0x40c49f…2af0
2 touches
0 conflicts
0x5f812db1…8681
0x40c49f…2af0
2 touches
0 conflicts
0x76d1e78d…7877
0x40c49f…2af0
2 touches
0 conflicts
0x8f56cada…b5a5
0x40c49f…2af0
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: 0x40c49f17…d22af0
1 conflict on slot 0x5d46e6a0b6…d15ed9
Audit this contract →
← previous block·next block →recent activity