← previous blocknext block →recent activity
Analyzing
Block #84,360,803
21 transactions · 16 stateful · 2026-06-29 00:57:42 UTC
Parallelism
86/100
Blocked
19%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,360,803 · 21 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
2w09w112w013w218w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e346a85…e9c5
0x34b655…2a6f
6 touches
3 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x07085204…98ab
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0xd8a49b87…5d96
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1fc046b…9af3
0x34b655…2a6f
4 touches
1 conflict
0x288123d4…728c
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 0x1e346a85f5…1ee9c5
Audit this contract →
← previous block·next block →recent activity