← previous blocknext block →recent activity
Analyzing
Block #84,130,424
16 transactions · 14 stateful · 2026-06-27 23:23:04 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,130,424 · 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
1w02w08w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2c29a4f…98af
0x40c49f…2af0
4 touches
1 conflict
0x8f6ea687…f342
0xa6afd3…d132
4 touches
1 conflict
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x5f682e71…9351
0xa6afd3…d132
3 touches
1 conflict
0x9c10aa6e…5a98
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
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: 0x40c49f17…d22af0
1 conflict on slot 0xa2c29a4f8b…f198af
Audit this contract →
← previous block·next block →recent activity