← previous blocknext block →recent activity
Analyzing
Block #84,500,843
20 transactions · 17 stateful · 2026-06-29 16:31:19 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,500,843 · 20 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
1w02w18w010w013w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x23ab8481…52d5
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xcbecfb96…3e12
0x405b63…7777
2 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
2 touches
0 conflicts
0xb54c8ced…5b8c
0x34b655…2a6f
2 touches
0 conflicts
0xc94da5de…7ca7
0x34b655…2a6f
2 touches
0 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity