← previous blocknext block →recent activity
Analyzing
Block #82,049,106
26 transactions · 26 stateful · 2026-06-18 07:47:18 UTC
Parallelism
27/100
Blocked
69%
Avg conflicts / tx
6.58
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #82,049,106 · 26 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w49w510w611w712w813w914w1015w1116w1217w1318w1419w1520w1621w1722w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x0b62b5…f373
38 touches
171 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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: 0x0b62b53e…a2f373
171 conflicts on slot 0x0000000000…000005
Audit this contract →
← previous block·next block →recent activity