← previous blocknext block →recent activity
Analyzing
Block #81,878,860
18 transactions · 16 stateful · 2026-06-17 12:50:29 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,878,860 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w27w08w19w215w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54a035dd…16c6
0x34b655…2a6f
7 touches
6 conflicts
0xf6476f21…3580
0x34b655…2a6f
6 touches
3 conflicts
0xb68e226d…c054
0xa6afd3…d132
6 touches
3 conflicts
0xc054838f…6696
0x34b655…2a6f
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0xd9aed890…c52f
0x34b655…2a6f
6 touches
3 conflicts
0xb838bbe6…2931
0x34b655…2a6f
4 touches
2 conflicts
0x82dd2252…e1ce
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
6 conflicts on slot 0x54a035dd92…5216c6
Audit this contract →
← previous block·next block →recent activity