← previous blocknext block →recent activity
Analyzing
Block #74,190,890
10 transactions · 9 stateful · 2026-05-12 22:07:44 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,190,890 · 10 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
2w03w17w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb3830b1…cbe0
0x34b655…2a6f
6 touches
3 conflicts
0x41335ddf…94b9
0x34b655…2a6f
6 touches
3 conflicts
0x8cc18498…ce7e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x902f6469…3c6b
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
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
3 conflicts on slot 0xfb3830b1d3…28cbe0
Audit this contract →
← previous block·next block →recent activity