← previous blocknext block →recent activity
Analyzing
Block #81,618,149
14 transactions · 13 stateful · 2026-06-16 07:53:26 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,618,149 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w110w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda51882a…e869
0x34b655…2a6f
6 touches
3 conflicts
0xb4c35fcd…43ae
0xa6afd3…d132
6 touches
3 conflicts
0x746619c8…1584
0x34b655…2a6f
4 touches
1 conflict
0x781f5487…d318
0x34b655…2a6f
4 touches
1 conflict
0x96194fbe…fa86
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xd99dd873…0df8
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
3 conflicts on slot 0xda51882a80…1ce869
Audit this contract →
← previous block·next block →recent activity