← previous blocknext block →recent activity
Analyzing
Block #84,331,322
12 transactions · 9 stateful · 2026-06-28 21:41:08 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,331,322 · 12 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
1w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04a63e8d…bf5d
0x0cc9b2…7777
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x316d6b00…9e5e
0x11ed3b…2c96
4 touches
1 conflict
0x00000000…0000
0xc3502e…1875
4 touches
1 conflict
0x00000000…0003
0x019883…2a9a
4 touches
1 conflict
0x40e2d65d…2a35
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
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: MONI (MONI)
1 conflict on slot 0x04a63e8d99…8dbf5d
Audit this contract →
← previous block·next block →recent activity