← previous blocknext block →recent activity
Analyzing
Block #84,488,220
33 transactions · 21 stateful · 2026-06-29 15:07:04 UTC
Parallelism
91/100
Blocked
43%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,488,220 · 33 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
2w03w04w16w17w28w010w114w015w116w218w021w022w123w130w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x44931115…3703
0x34b655…2a6f
4 touches
1 conflict
0x7201bdec…0fca
0x34b655…2a6f
4 touches
1 conflict
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0xa1e51cc8…e4cf
0x34b655…2a6f
4 touches
1 conflict
0xee757899…302b
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity