← previous blocknext block →recent activity
Analyzing
Block #84,047,945
15 transactions · 13 stateful · 2026-06-27 14:13:30 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,047,945 · 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
1w02w15w06w17w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd10e72b…c630
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb30e1191…9e3c
0x34b655…2a6f
4 touches
1 conflict
0xde696e46…6446
0x34b655…2a6f
3 touches
1 conflict
0x12dbe63f…637d
0x40c49f…2af0
2 touches
0 conflicts
0x5f630735…196b
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 0xcd10e72b03…65c630
Audit this contract →
← previous block·next block →recent activity