← previous blocknext block →recent activity
Analyzing
Block #73,042,574
16 transactions · 14 stateful · 2026-05-07 14:27:52 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,042,574 · 16 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
1w02w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0xafd59af5…5257
0xc8689a…ee79
4 touches
1 conflict
0xeb0915f1…c150
0x34b655…2a6f
4 touches
1 conflict
0xcfbcec0b…68a5
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0x8d3166c4…7cfb
0x34b655…2a6f
4 touches
1 conflict
0x0f9b918b…212d
0x34b655…2a6f
4 touches
1 conflict
0x20ac0567…c954
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
1 conflict on slot 0x6f6fc26c68…133e34
Audit this contract →
← previous block·next block →recent activity