← previous blocknext block →recent activity
Analyzing
Block #81,019,713
12 transactions · 9 stateful · 2026-06-13 13:27:29 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,019,713 · 12 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
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x366748e9…1282
0x34b655…2a6f
4 touches
1 conflict
0x6396a4c4…f626
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xa515c124…15f6
0x065c9d…c394
2 touches
0 conflicts
0xd1ce7ff1…57f5
0x065c9d…c394
2 touches
0 conflicts
0xfd5d2d48…2cd2
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity