← previous blocknext block →recent activity
Analyzing
Block #81,030,161
13 transactions · 11 stateful · 2026-06-13 14:37:04 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,030,161 · 13 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
4w05w16w09w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc63b2ce3…9fb8
0x96b79e…d00a
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x828cefbb…7934
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
3 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: 0x96b79ef4…d2d00a
1 conflict on slot 0xc63b2ce306…b99fb8
Audit this contract →
← previous block·next block →recent activity