← previous blocknext block →recent activity
Analyzing
Block #74,224,549
11 transactions · 10 stateful · 2026-05-13 01:51:39 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,224,549 · 11 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
4w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xa26c29a3…c434
0x34b655…2a6f
4 touches
1 conflict
0xb0f1bb77…88de
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
2 touches
0 conflicts
0x2cb746ba…fedc
0x065c9d…c394
2 touches
0 conflicts
0x3d2dd4b4…351d
0x065c9d…c394
2 touches
0 conflicts
0x5b754c9c…1e4e
0x065c9d…c394
2 touches
0 conflicts
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 0x768cffcdb0…d12648
Audit this contract →
← previous block·next block →recent activity