← previous blocknext block →recent activity
Analyzing
Block #73,187,392
17 transactions · 17 stateful · 2026-05-08 06:31:28 UTC
Parallelism
47/100
Blocked
59%
Avg conflicts / tx
2.29
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,187,392 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
18 touches
36 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x9fd24ec1…1ffb
0x065c9d…c394
2 touches
0 conflicts
0xaa0cf412…2a1f
0x065c9d…c394
2 touches
0 conflicts
0xc0c9dab7…faae
0x065c9d…c394
2 touches
0 conflicts
0xe1869a91…fba0
0x065c9d…c394
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
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: 0xab35264b…1cfa38
36 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity