← previous blocknext block →recent activity
Analyzing
Block #84,573,797
18 transactions · 17 stateful · 2026-06-30 00:38:19 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,573,797 · 18 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
1w02w16w015w016w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x1aad9f80…051d
0x5afd3e…7620
4 touches
1 conflict
0xf9005054…cbf7
0x5afd3e…7620
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x594e0298…d1ab
0x065c9d…c394
2 touches
0 conflicts
0xe1c31e16…8cb9
0x065c9d…c394
2 touches
0 conflicts
0x40970e69…da50
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity