← previous blocknext block →recent activity
Analyzing
Block #82,267,157
27 transactions · 21 stateful · 2026-06-19 08:01:45 UTC
Parallelism
85/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,267,157 · 27 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
1w03w04w05w16w17w08w09w110w011w115w216w317w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x9cc13b7b…c0ac
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e1c3586…83d7
0xa6afd3…d132
4 touches
1 conflict
0xfe3d37ee…6e67
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
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
1 conflict on slot 0xa92c87634b…146d7f
Audit this contract →
← previous block·next block →recent activity