← previous blocknext block →recent activity
Analyzing
Block #81,630,259
15 transactions · 14 stateful · 2026-06-16 09:14:02 UTC
Parallelism
87/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,630,259 · 15 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
2w05w06w17w010w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb428a976…7cf0
0x34b655…2a6f
4 touches
1 conflict
0xdbb623a1…1f9d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x049790d7…e6f9
0x065c9d…c394
2 touches
0 conflicts
0x0f0bac2f…798c
0x065c9d…c394
2 touches
0 conflicts
0x35a578a7…a131
0x065c9d…c394
2 touches
0 conflicts
0x4035d387…e5bc
0x065c9d…c394
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: Perpl
1 conflict on slot 0xb428a97603…637cf0
Audit this contract →
← previous block·next block →recent activity