← previous blocknext block →recent activity
Analyzing
Block #71,043,576
25 transactions · 21 stateful · 2026-04-28 08:22:55 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,043,576 · 25 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
8w09w111w014w015w116w017w118w219w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
8 touches
6 conflicts
0x4ab14837…e1b2
0x2a68ba…90c5
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x131a2e…0da9
6 touches
4 conflicts
0x00000000…003d
0x131a2e…0da9
6 touches
3 conflicts
0x116a621e…f97f
0x34b655…2a6f
4 touches
1 conflict
0x3c35979a…975d
0x34b655…2a6f
4 touches
1 conflict
0x3d6ad949…c225
0x34b655…2a6f
4 touches
1 conflict
0x5f02eb78…3afe
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 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity