← previous blocknext block →recent activity
Analyzing
Block #72,497,297
14 transactions · 11 stateful · 2026-05-05 01:55:16 UTC
Parallelism
79/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,497,297 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w09w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3981be5…2c47
0x34b655…2a6f
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x9e719c7a…df63
0x34b655…2a6f
4 touches
1 conflict
0xa433ef1c…2a52
0x34b655…2a6f
4 touches
1 conflict
0xa486f342…64d5
0x34b655…2a6f
4 touches
1 conflict
0xcb63cb0a…66a9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
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
3 conflicts on slot 0xf3981be56e…f02c47
Audit this contract →
← previous block·next block →recent activity