← previous blocknext block →recent activity
Analyzing
Block #84,497,191
16 transactions · 14 stateful · 2026-06-29 16:06:56 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,497,191 · 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
2w04w17w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb4d69e7…3c51
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd106c60d…6cdb
0x065c9d…c394
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x392ba1ca…053e
0x065c9d…c394
3 touches
1 conflict
0x17255e13…30b2
0x065c9d…c394
3 touches
1 conflict
0x6acc4afc…e7db
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xfb4d69e7db…6c3c51
Audit this contract →
← previous block·next block →recent activity