← previous blocknext block →recent activity
Analyzing
Block #84,094,276
13 transactions · 10 stateful · 2026-06-27 19:22:14 UTC
Parallelism
85/100
Blocked
30%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,094,276 · 13 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
2w03w15w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16dce2e7…6f05
0x34b655…2a6f
4 touches
1 conflict
0x675fbe8f…509f
0x34b655…2a6f
4 touches
1 conflict
0x995addb1…6b26
0x065c9d…c394
4 touches
1 conflict
0x21c2cd87…ed6f
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1349aa49…4a25
0xbeeffb…5fdb
2 touches
0 conflicts
0xa808ec60…5528
0xbeeffb…5fdb
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 0x16dce2e7df…1b6f05
Audit this contract →
← previous block·next block →recent activity