← previous blocknext block →recent activity
Analyzing
Block #81,877,556
27 transactions · 23 stateful · 2026-06-17 12:41:49 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,877,556 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w05w16w18w09w010w114w115w217w118w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a2c83a3…a29a
0x34b655…2a6f
8 touches
6 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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: Perpl
6 conflicts on slot 0x7a2c83a30a…f3a29a
Audit this contract →
← previous block·next block →recent activity