← previous blocknext block →recent activity
Analyzing
Block #73,036,346
29 transactions · 19 stateful · 2026-05-07 13:46:26 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,036,346 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w217w018w119w220w324w125w226w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x0b390c61…dc07
0x065c9d…c394
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe72962f6…e169
0x8d66a4…3095
6 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x0de7749d…5bef
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
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
6 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity