← previous blocknext block →recent activity
Analyzing
Block #81,626,835
23 transactions · 18 stateful · 2026-06-16 08:51:15 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,626,835 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w17w09w110w211w312w013w014w115w218w121w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0xc7a15219…7745
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x55bdd4ba…6a63
0x34b655…2a6f
4 touches
1 conflict
0x5b9b676a…81d9
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
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: 0xaa7ee7ce…aff0e4
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity