← previous blocknext block →recent activity
Analyzing
Block #84,357,194
15 transactions · 13 stateful · 2026-06-29 00:33:36 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,357,194 · 15 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
1w02w13w18w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2c071e1…a430
0x34b655…2a6f
4 touches
1 conflict
0xd16ba145…d030
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7464b23e…4b9e
0xa6afd3…d132
3 touches
1 conflict
0x8653c5c3…246d
0x065c9d…c394
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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 0xb2c071e1e6…f0a430
Audit this contract →
← previous block·next block →recent activity