← previous blocknext block →recent activity
Analyzing
Block #72,458,362
11 transactions · 10 stateful · 2026-05-04 21:36:07 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,458,362 · 11 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
1w02w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1dda4742…54d4
0x065c9d…c394
2 touches
0 conflicts
0x30d737f7…0ffb
0x065c9d…c394
2 touches
0 conflicts
0x32b3e556…42aa
0x065c9d…c394
2 touches
0 conflicts
0x8f928f69…2f2a
0x065c9d…c394
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: 0x7e9d3a8a…4f9fda
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity