← previous blocknext block →recent activity
Analyzing
Block #84,200,847
14 transactions · 12 stateful · 2026-06-28 07:11:42 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,200,847 · 14 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
8w09w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfd784183…67bb
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x36e9d198…2607
0x0ab36e…9ac7
2 touches
0 conflicts
0x50e82744…27bc
0x0ab36e…9ac7
2 touches
0 conflicts
0xb22e08d6…358b
0x0ab36e…9ac7
2 touches
0 conflicts
0xce0963f4…7761
0x0ab36e…9ac7
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 0x6f132c01d5…7dcdcd
Audit this contract →
← previous block·next block →recent activity