← previous blocknext block →recent activity
Analyzing
Block #73,037,048
21 transactions · 16 stateful · 2026-05-07 13:51:06 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,037,048 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w110w014w115w218w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4730a2d…3538
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0xfdb9512f…2cc2
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
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 0xf4730a2de3…ef3538
Audit this contract →
← previous block·next block →recent activity