← previous blocknext block →recent activity
Analyzing
Block #84,041,264
17 transactions · 16 stateful · 2026-06-27 13:29:04 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,041,264 · 17 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
1w02w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd01910c9…9418
0x34b655…2a6f
4 touches
1 conflict
0xf4270ac4…ca03
0x5afd3e…7620
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x390332e8…e067
0x5afd3e…7620
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
2 touches
0 conflicts
0x8b80a24c…7312
0x754704…b603
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 0xd01910c9e4…799418
Audit this contract →
← previous block·next block →recent activity