← previous blocknext block →recent activity
Analyzing
Block #84,361,331
16 transactions · 12 stateful · 2026-06-29 01:01:13 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,361,331 · 16 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
8w010w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa8e3cd…af20
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7dc64b2c…05e7
0x34b655…2a6f
4 touches
1 conflict
0x9877900a…1e07
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0xd4e7949d…dad2
0x34b655…2a6f
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 0x0aa8e3cd13…0baf20
Audit this contract →
← previous block·next block →recent activity