← previous blocknext block →recent activity
Analyzing
Block #84,240,224
14 transactions · 12 stateful · 2026-06-28 11:34:14 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,240,224 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dbefc67…4855
0x34b655…2a6f
4 touches
1 conflict
0x9eaae86e…12be
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x7c0e2f2b…2e58
0x5afd3e…7620
2 touches
0 conflicts
0xf2b4cdfb…15b5
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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 0x9dbefc672a…064855
Audit this contract →
← previous block·next block →recent activity