← previous blocknext block →recent activity
Analyzing
Block #84,600,345
13 transactions · 10 stateful · 2026-06-30 03:35:08 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,600,345 · 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
1w02w16w07w08w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8607b9d8…ad3b
0x34b655…2a6f
4 touches
1 conflict
0x98e95e72…24dd
0x34b655…2a6f
4 touches
1 conflict
0xbc9aaf19…8cfd
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7585925a…3f45
0x34b655…2a6f
4 touches
1 conflict
0x489d307f…3a6f
0x40c49f…2af0
2 touches
0 conflicts
0x4bcb740a…b738
0x40c49f…2af0
2 touches
0 conflicts
0xbc51e84a…e549
0x40c49f…2af0
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 0x8607b9d816…96ad3b
Audit this contract →
← previous block·next block →recent activity