← previous blocknext block →recent activity
Analyzing
Block #72,100,179
14 transactions · 10 stateful · 2026-05-03 05:42:38 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,100,179 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
14 touches
21 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x248b1c5d…a1d4
0x065c9d…c394
2 touches
0 conflicts
0x7edae8df…d3f5
0x065c9d…c394
2 touches
0 conflicts
0xb8ddd545…2d82
0x065c9d…c394
2 touches
0 conflicts
0xd0e2fd6a…5379
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: 0x7e9d3a8a…4f9fda
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity