← previous blocknext block →recent activity
Analyzing
Block #81,628,025
13 transactions · 12 stateful · 2026-06-16 08:59:12 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,628,025 · 13 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
1w04w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3c96942…f0fc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x11e88ed4…7e55
0x065c9d…c394
3 touches
1 conflict
0xd5e76092…e223
0x065c9d…c394
3 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x5e9a21fc…196d
0x065c9d…c394
2 touches
0 conflicts
0x608530db…05f8
0x065c9d…c394
2 touches
0 conflicts
0x66fe6ebb…5731
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 0xb3c9694250…dbf0fc
Audit this contract →
← previous block·next block →recent activity