← previous blocknext block →recent activity
Analyzing
Block #81,019,651
19 transactions · 13 stateful · 2026-06-13 13:27:04 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,019,651 · 19 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c737379…86fb
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d1a1
0xb327fb…6b13
3 touches
1 conflict
0x9abd5cd0…9d1d
0xb327fb…6b13
3 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
2 touches
0 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
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 0x6c7373790e…ff86fb
Audit this contract →
← previous block·next block →recent activity