← previous blocknext block →recent activity
Analyzing
Block #72,458,368
12 transactions · 9 stateful · 2026-05-04 21:36:09 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,458,368 · 12 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
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1728ed63…499c
0xea1b8e…c5ec
4 touches
1 conflict
0xc079cc93…b57b
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
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
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: LeverUp: LeverUp
1 conflict on slot 0x1728ed6317…a9499c
Audit this contract →
← previous block·next block →recent activity