← previous blocknext block →recent activity
Analyzing
Block #81,878,255
24 transactions · 20 stateful · 2026-06-17 12:46:26 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,878,255 · 24 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
1w02w03w05w16w210w011w312w415w016w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xfcb9138a…3830
0xc8689a…ee79
6 touches
3 conflicts
0xa72e521d…f873
0x34b655…2a6f
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0xc3a62990…9759
0x34b655…2a6f
6 touches
3 conflicts
0xcf17589f…048c
0x34b655…2a6f
6 touches
3 conflicts
0xe994dc03…e3a6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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: Perpl
6 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity