← previous blocknext block →recent activity
Analyzing
Block #72,172,889
8 transactions · 7 stateful · 2026-05-03 13:47:01 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,172,889 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcbad3868…f129
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2c0bd34f…5547
0x065c9d…c394
2 touches
0 conflicts
0x43b6de13…6d6f
0x065c9d…c394
2 touches
0 conflicts
0x785ca15f…2f4d
0x065c9d…c394
2 touches
0 conflicts
0xc1825e0d…57a4
0x065c9d…c394
2 touches
0 conflicts
0xcf4f43e6…4b81
0x065c9d…c394
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 0xcbad3868be…19f129
Audit this contract →
← previous block·next block →recent activity