← previous blocknext block →recent activity
Analyzing
Block #84,075,379
29 transactions · 23 stateful · 2026-06-27 17:16:12 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,075,379 · 29 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w312w013w114w215w316w420w524w425w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32359294…7113
0x34b655…2a6f
10 touches
10 conflicts
0x3de5fb8b…400a
0xa6afd3…d132
10 touches
10 conflicts
0x1d2a8430…30bf
0xa6afd3…d132
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0x19ce481d…6c36
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x3235929431…327113
Audit this contract →
← previous block·next block →recent activity